Nagios Core logins with XI

[uidaho]

I am having trouble where some users are not able to use their XI username/passwords to login into Nagios Core web interface.

Nagios core still has some very useful functionality that is not in Nagios XI. In particular, the ability to view the resultant configurations for all hosts and services (http://nagios01/nagios -> Configuration -> Services). We heavily use templates and hostgroups. It is very useful for us to expose the resultant configs to all of the systems administrators. It is a great tool for troubleshooting a broken monitor.

However, some of the users are not able to log into core. Their username/password works fine in the XI web interface, but not through with the core web interface.

How can I troubleshoot this? How does Core use the XI accounts to authenticate? Does XI drop the accounts/passwords to a .htaccess file somewhere?

Any tips would be greatly appreciated.

[BanditBBS]

I think when creating the XI user you need to make sure and check the box "Create as monitoring contact" also. Without that, they'd have no access to Core.

I never tested this though, so don't believe anything I just said, it's just a thought.

EDIT: See the next post for a proper answer as apparently I was wrong...so basically, ignore me

[slansing]

You can create new users without specifying a monitoring contact. Are these users normal users or admins? Have you logged out of the xi interface and back in as one of those users prior to trying to log into core with it? I was not able to reproduce your problem after doing the previous step.

[lmiltchev]

slansing is correct - you don't have to create a XI user that is also a monitoring contact. However, you need to log in at least once into the Nagios XI web interface as this new user and accept the license agreement. After this the user will be able to log into the Nagios Core web interface as well.

[uidaho]

These users were non-admins. I actually did try switching them to admin accounts, but I didn't think to make them log out/back in again.

Solution found - the users must be admins to have access to core. (and must log out/back in to apply the changes to their account).

Thanks!