Hello:
We are running Nagios XI 5.2.0 and like the new interface and new integration components (especially LDAP/AD).
We are experiencing an issue, though, with trying to identify why an imported Active Directory account would prompt to change it's password after logging on to Nagios XI?
We went to Admin - Manage Users, then selected the imported Active Directory account (we'll call it ServiceAdmin), and identified the General Settings, Preferences, Security Settings, and Authentication Settings, but there was no "Force Password Change at Next Login:" option like the one identified in a Local Auth Type: Nagios XI user account.
Why would Nagios XI prompt to change an imported Active Directory user account password? I thought perhaps a user template, but that doesn't appear to be the case.
Lastly, when I click on the select box to the left of "Username" to select all users, none of the usernames' selection box is selected - I have to select each individual box.
User Management issue ...
Re: User Management issue ...
Can you edit that account, change the Auth Type to local user and is the Force Password Change at Next Login: box checked?
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: User Management issue ...
tgriep wrote:Can you edit that account, change the Auth Type to local user and is the Force Password Change at Next Login: box checked?
Yes it was.
So the Local User "Force Password Change" option that is set for the Local user Auth Type, which is not an option for the LDAP or Active Directory Auth type, is being applied? Sounds like an "enhancement"/"feature" that needs to be fixed, along with the select all box not working.
Newbie '14
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: User Management issue ...
This can happen in 5.2.0 if you create a new user and do not untick the box.
We are aware of this bug, and the next bug fix release will not allow this flag to remain set.
We are aware of this bug, and the next bug fix release will not allow this flag to remain set.