-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
9.12.12, 10.6.0
-
None
-
9.12
-
2
-
Severity 3 - Minor
-
18
-
Issue Summary
Inactive (and deleted) LDAP users are not being replaced by their active accounts.
This can happen in the following scenario:
- The user present in the 1st User Directory:
- Had data associated to them;
- Was removed from the LDAP or from the location configured in Jira, causing Jira to show the user as inactive/deleted ("
MorimotS[X]") status
- Then, a 2nd Directory was added into Jira with an active copy of the same user
Steps to Reproduce
- Considering the following directory order:
- Active Directory - LDAP1
- Internal Jira Directory
- LDAP1 is enabled in Jira with the following user object filter:
(&(objectCategory=Person)(sAMAccountName=*)(memberOf=CN=apac-users*))
- Account "MorimotS" is active on LDAP1 and must create an issue in Jira
- In LDAP, remove the user from group "apac_users" or delete the user completely
- Run Full Synchronization for LDAP1
- User shows up in Jira with deleted status "
MorimotS[X]" - Disabled LDAP1
- Created a new account "MorimotS" in your Jira Internal directory
- At this moment, we can properly see the active account from the Jira Internal Directory being displayed
- Re-enable LDAP1 keeping this LDAP on top
- Run a new Full LDAP Synchronization
Expected Results
The active account from Jira Internal Directory should be displayed
Actual Results
The inactive/deleted account ("MorimotS [X]") is being displayed instead of the active account, keeping the user from authenticating.
Workaround
- In your LDAP1, re-add the user into the group or recreate the user
- Run a Full LDAP Synchronization in Jira
- You should notice that Jira has changed the status of the LDAP user to active
- Once again, delete the user or remove the user from the group
- Run a Full LDAP Synchronization in Jira
- As a result, the active account from your 2nd User Directory will be displayed