Hi all, We've recently started to upgrade from Nagios 2.7 to 3.1 and noticed something odd.
We use .htaccess with Apache in the Nagios webroot to restrict authentication to only our internal LDAP system. Once auth'd Nagios' cgi.conf then defines which users have which perms. Users coming from our "protected" IP space don't have to auth at all and get the default user of guest. This has been working fine for us over the last year or two, but since trying to move to 3.1 the same method and config files are giving us different behavior. After authenticating succesfully as user "bob", Nagios doesn't pick up bob as the auth'd name and just sees me as the default "guest". Which means bob's Nagios perms are not activated, guest's are. No matter what I've tried I can't get Nagios to accept the authenticated user name from Apache, yet I have this working fine in 2.7 with identical configs. Anyone else seen the same behavior or have any ideas? This really has me stumped and is a blocker for us upgrading. Thanks, -Dave -- ================================ David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu ================================ ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Nagios-users mailing list Nagios-users@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
