On 8 June 2010 14:50, Jason Gauthier <[email protected]> wrote: > All, > > > I am fighting with a permission issue I cannot seem to figure out. > > Here is the important pieces of my cgi configuration: > > use_authentication=1 > default_user_name= > authorized_for_system_information= > authorized_for_system_commands=jack,jill,john,dave,bob,tim > authorized_for_configuration_information=jack,jill,john,dave,bob,tim > authorized_for_all_hosts=jack,jill,john,dave,bob,tim > authorized_for_all_host_commands jack,jill,john,dave,bob,tim > authorized_for_all_services=jack,jill,john,dave,bob,tim > authorized_for_all_service_commands=jack,jill,john,dave,bob,tim > > When "dave" attempts to issue a service command (enable notifications) > they receive this error: > > "Sorry, but you are not authorized to commit the specified command" > > None of the other users do. So, in an effort to troubleshoot, I > removed ALL users except for dave. > Dave still cannot process the command, but jack still can! > > When jack attempts to view the configuration, he is also denied now. > This implies that the permissions are being acknowledged to some degree. > I revert the changes back above. Jack can still execute commands (dave > cannot), but both jack and dave can view the configuration. > > What is going on with dave? Can I enable some logging perhaps to help > determine the root cause? > > Thanks! >
Bit of a long shot but I wonder if there's a non-printing character in your cgi.cfg somewhere where it shouldn't be. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Nagios-users mailing list [email protected] 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
