Non Admin Users not able to set downtime

[WillemDH]

Hello,

Just discovered today that users without admin level permissions seem unable to set downtime for hosts. I tried with two different users, they all seem to have the same issue. Admins do not experience this issue. Check the screenshot for the configured permissions. Can someone test if this is reproducable?

What can I do to fix this?

EDIT: I changed a user to admin and he still can't set downtime for a host. Setting downtime with external commands does still work. Me and another admin user also can still set downtime. When I masquearade as the user that ahs the issue i'm also not able to set downtime.

Grtz

Willem

[lmiltchev]

I was not able to recreate the issue. My users can schedule downtime for hosts/services - no issues whatsoever.

Are these local or AD/LDAP users? Is this a "new" install or an upgrade from an older version of XI? Do you see the correct permissions in the cgi.cfg?

Code: Select all

grep <username> /usr/local/nagios/etc/cgi.cfg

Do you see any errors in the web UI or in the apache error log?

[WillemDH]

All our users except nagiosadmin are AD users. It is our production server which has been upgraded over the past 2,5 years.

Checking cgi.cfg tells me the users has:
- authorized_for_all_host_commands
- authorized_for_all_hosts
- authorized_for_all_service_commands
- authorized_for_all_services
- authorized_for_configuration_information
- authorized_for_system_commands
- authorized_for_system_information

As the user is an admin now, I'm guessing this is correct. I tried rebooting the server and tested again with one of the users (the one who is now admin) experiencing the issue and he still can't schedule downtime.

We need this to work again asap, so I will create en email support ticket.

Grtz

[rkennedy]

There was a similar issue the other day that happened, and it related to having the 'read-only' option applied. I see in your screen shot it isn't checked - but, was it on any of the users?

[WillemDH]

None of the users I know that experience the issue have the read-only checkbox checked.

[ssax]

Locking to continue in the ticket.