Duplicate user if changed the username on AD account?

[dhkivan]

We use LDAP sync to import users from AD, if changed the username in AD which this account is already imported to database, then it will be created a new user in database on next LDAP sync?

If yes, can avoid it, for example check the employeeID or SID of user account or else?

[snipe]

Throughout the system, we use username as the identifying key, so i’m not sure there’s a good workaround here. To have it use employee ID (which many organizations don’t use) would break things in all kinds of new and awful ways.

[dhkivan]

Agreed to use username, just think can add an additional checking at LDAP sync process, e.g use employeeid or sid to double verify the account whether is exisit or not.

And what's the purpose of employee no. in the system?

[snipe]

And what's the purpose of employee no. in the system?

It has no purpose other than being an additional piece of information some companies choose to track with the users/assets. Not everyone uses employee ID, so we can't base business logic around it.

[stale]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[stale]

This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.