You don't want to be stuck with administering Nagios all by yourself, but you want to add some junior admins to help out.
Your new admins must have system accounts on the Nagios server, and passwords in htpasswd.users:
# useradd -m -G nagioscmd admin2
# passwd admin2
# htpasswd /usr/local/nagios/etc/htpasswd.users admin2
Then, you need to configure access to whatever Nagios functions you want them to have in cgi.cfg, using comma-delimited lists like this example shows:
authorized_for_all_services=nagios,admin2
authorized_for_all_hosts=nagios,admin2
Restart Nagios to activate the changes:
# /etc/init.d/nagios restart
Do not have any user in the nagios gro************up but nagios.
These aren't the most fine-grained access controls, but they do let you limit what your underlings can do:
authorized_for_system_information
View Nagios process information.
authorized_for_configuration_information
View all configuration information, both hosts and commands.
authorized_for_system_commands
Shutdown, restart, and put Nagios on standby.
authorized_for_all_services,
authorized_for_all_hosts
View information for all hosts and services. By default, Nagios users can only view hosts or services they are named as contacts for.
authorized_for_all_service_commands,
authorized_for_all_host_commands
Issue service or host commands. By default, Nagios users can only run commands for the hosts or services they are named as contacts for.
"CGI Configuration File Options": http://localhost/nagios/docs/configcgi.html
"Authentication And Authorization In The CGIs":
http://localhost/nagios/docs/cgiauth.html |
Nagios.org: http://www.nagios.org/