Our Jira syncs to an LDAP directory. When a user leaves the organization, their LDAP account is deleted, but the profile remains in Jira. That will sometimes cause issues when new LDAP users are provisioned who may have similar names. The new LDAP account will sync to Jira and combine the new and old users into a single corrupted profile.
Example: Mike Smith (LDAP: Smith_M) leaves the company. He has many contributions in Jira, so his profile cannot be deleted. A few months later, Melissa Smith (Smith_M) is created in LDAP and also syncs to Jira. Now Melissa's account (Smith_M) is merged with Mike's account (also Smith_M) and a number of conflicts result. Mike's old work displays under Melissa's name (intermittently), or Melissa's account will reflect Mike's login history and avatar, etc.
How can we use an LDAP directory and avoid these conflicts?
Running Server 8.13
We use the sAMAccountName attribute for usernames and every employee has Unique number ID. We have managed to avoid the problem you explained that way.
Thanks,
Tim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.