HTTP Auth -> Nagios problem

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Matthew Brennan
> Sent: Sunday, November 06, 2005 2:39 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] HTTP Auth -> Nagios problem
> 
> I have setup Nagios on other boxes without error, but I just put it
> on a new box and am experiencing a problem. I have enable HTTP
> authentication via .htaccess, I auth to HTTP fine but Nagios shows me
> as 'logged in a ?' - I set a default user in the cgi.cfg to override
> temporarily, but i can't figure out whats wrong. It is kind of
> important I get this working as not all users are supposed to be
> allow to see / manipulate all hosts. If anyone has any information
> that may help me it would be appreciated. (Nagios v2.0b4 - Apache
> v2.0.53) Thank you.

Make sure your .htaccess file is in the ~nagios/sbin directory, not
[just] ~nagios/share.

You might want to also locate a perl or other script on the web that
prints out the CGI environment variables. Drop that in the protected
directory and make sure that Apache is properly setting the REMOTE_USER
environment variable. Nagios has no authentication routines and relies
on Apache handling that.

If that's not it, give us _specifics_ about what you did to set it up
(step by step) and the troubleshooting you've done so that we can help
figure out what's out of place.

--
Marc


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null