I do use Likewise-Open for authentication to the system, but I was trying to make the Apache authentication completely independent. For some reason, until you asked me that, it didn't even occur that there could be a conflict between the two. I just tried adding a completely different user (michellea is the active directory user name), and that works perfectly fine. Apparently the two of them were conflicting. Thank you! <div class="gmail_quote">On Tue, Jan 26, 2010 at 2:05 PM, Matt Simmons <<a href="mailto:standalone.sysadmin@gmail.com">standalone.sysadmin@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> You aren't using Likewise-Open for your AD authentication, are you? --Matt <div><div></div><div class="h5"> On Tue, Jan 26, 2010 at 1:54 PM, Michelle Avery <<a href="mailto:michelleavery8@gmail.com">michelleavery8@gmail.com</a>> wrote: > I originally set up my nagios environment with an administrative user named > nagiosadmin and basic authentication. At that time everything worked fine. > I tried to set up Active Directory authentication, but that caused numerous > problems, including the fact that my Active Directory users couldn't do > things like re-schedule service checks. At the time, I thought this was an > AD issue. I have since decided to abandon AD authentication altogether, > although I'm now using Digest authentication (per the official > documentation) instead of Basic. Now, however, I'm still finding that I > can't re-schedule service checks (or schedule downtime) as any user other > than nagiosadmin. I have created passwords for both users in my .digest_pw > file. My cgi.cfg file shows: > > physical_html_path=/usr/share/nagios3/htdocs > url_html_path=/nagios3 > use_authentication=1 > default_user_name= > authorized_for_system_information=michellea,nagiosadmin > authorized_for_system_commands=michellea,nagiosadmin > authorized_for_configuration_information=michellea,nagiosadmin > authorized_for_all_hosts=michellea,nagiosadmin > authorized_for_all_host_commands=michellea,nagiosadmin > authorized_for_all_services=michellea,nagiosadmin > authorized_for_all_service_commands=michellea,nagiosadmin > default_statusmap_layout=5 > default_statuswrl_layout=4 > refresh_rate=90 > ping_syntax=/bin/ping -n -U -c 5 $HOSTADDRESS$ > main_config_file=/etc/nagios3/nagios.cfg > > The user michellea is also set as a contact for all of the hosts. When I log > in to the web interface, it shows "Logged in as michellea." I can see all > information for all hosts and services, but I still can't issue commands. > What am I missing? > > Michelle > </div></div>> ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > <a href="http://p.sf.net/sfu/theplanet-com" target="_blank">http://p.sf.net/sfu/theplanet-com</a> > _______________________________________________ > Nagios-users mailing list > <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> > <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> > ::: Please include Nagios version, plugin version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -- LITTLE GIRL: But which cookie will you eat FIRST? COOKIE MONSTER: Me think you have misconception of cookie-eating process. </blockquote></div>