Redhat – I can’t log in to Nagios web interface

apache-2.2monitoringnagiosredhat

When i try to login to Nagios in my web browser and after having repeatedly enter my login and password on my Nagios page http://127.0.0.1/nagios/, i get this :

Authorization Required

This server could not verify that you are authorized to access the
document requested. Either you supplied the wrong credentials (e.g.,
bad password), or your browser doesn't understand how to supply the
credentials required. Apache/2.2.15 (Red Hat) Server at 127.0.0.1 Port
80

I changed the password :

htpasswd -c /etc/nagios/htpasswd.users nagiosadmin

And restart the server :

service httpd restart

But without result !

Best Answer

<Directory "/usr/lib/nagios/cgi-bin/">
   Options ExecCGI
   AllowOverride None
   Order allow,deny
   Allow from all
   AuthName "Nagios Access"
   AuthType Basic
   AuthUserFile /etc/nagios/passwd
   Require valid-user
</Directory>

You have specified the wrong path for AuthUserFile: it should be /etc/nagios/htpasswd.users instead of /etc/nagios/htpasswd.

Related Solutions

Php – Seamless SSO with Kerberos, IE, Firefox, LDAP Active Directory

We faced a very similar problem. We eventually concluded that while integrated NTLM logon support in Internet Explorer and Firefox is convenient, there are so many exception cases which result in failure that we changed our approach.

The problem with integrated authentication is that it works only when the currently logged on username and password are still correct and properly authorized to access the resource.

There are more circumstances where it doesn't work however:

If the username and/or password are incorrect, there's no way to use alternate credentials as you stated above
If the account and/or password have expired or if the password is wrong, the browser will return an "unauthorized" message with no clue as to which of the problems it is

The approach we standardized on was to put up a username/password logon web page (in front of the application) which accepts the credentials. When the credentials are submitted, the application would in turn validate those credentials against the directory and then respond accordingly (in a .NET world you could use Forms Authentication http://msdn.microsoft.com/en-us/library/aa480476.aspx to force access to the application via this login page). Since the application is doing the credential validation, you get rich information as to the nature of the login failure. In addition, even if the login succeeds but there's relevant information to display to the user, e.g. their password will expire shortly, etc., this provides an opportunity to do so.

UPDATE: I forgot to mention that if you adopt this approach, you'll need to allow anonymous access to the IIS application root. This will allow access to the login web page without first attempting the automatic NTLM authentication. It's up to you whether you leave NTLM authentication enabled; perhaps you do want some clients to still automatically log in.

Redhat – Basic Apache httpd server setup becomes slow to serve images requiring frequent restart

A couple questions:

Have you done any tuning to the Apache.conf file? Which Apache MPM are you using?
What parameters are currently set in the Apache.conf file for:

Timeout
KeepAlive
MaxKeepAliveRequests
KeepAliveTimeout
MinSpareServers
MaxSpareServers
StartServers
MaxClients
MaxRequestsPerChild

Best Answer

Related Solutions

Php – Seamless SSO with Kerberos, IE, Firefox, LDAP Active Directory

Redhat – Basic Apache httpd server setup becomes slow to serve images requiring frequent restart

Related Topic