"Logged in as user" vs. "Logged in as [email protected]"

[teh0015]

I have a couple core 4.1.1 machines I admin.
One of the core machines (S1) shows "Logged in as user@domain" instead of just "user"
Access to the web interface on S1 is pretty restrictive.
Only a small group can touch the web interface and they are specifically defined in cgi.cfg as having access to modify all machines.
I wanted to add a user that just has the default access to the machines they are listed as contacts on, which is how I have another core machine configured (and it works fine but it's a different group).
Unfortunately, while the user get past the auth box, they can't see anything unless I explicitly add the user to authorized_for_all_services* (etc) in cgi.cfg.
S1 is using auth_kerb_module and my other core instances are using auth_ldap.
I noticed that when I log into S1 I'm listed as '[email protected]' while on the other instance it's just 'user' - so I created a contact definition on S1 using '[email protected]' and permissions work as expected.

So is the passing of 'user' vs. '[email protected]' controlled by Nagios, Apache, or the module ?

[avandemore]

That would be defined as the Apache basic auth user eg htpasswd. For XI, that's like this:

Code: Select all

# strings /usr/local/nagiosxi/etc/htpasswd.users
nagiosadmin:{SHA}string=
nagiosxi:{SHA}string=

Permissions in Core are discussed here:
https://assets.nagios.com/downloads/nag ... iauth.html