When Jive is set up to sync users through an LDAP system such as Azure Active Directory, if the LDAP system administrator deletes or disables a user account in the LDAP system and then recreates the user account with the same user details such as name, email address, etc, it causes Jive to also disable the user's account in the Jive instance and recreate a new user account.
When the user logs in to Jive, they will see a fresh user account with none of their old Jive settings or Content.
This behavior is observed when you have the following settings enabled in your Jive instance
- Deactivate federated user accounts not found in the directory
- Provision new user account upon initial login
Why is the old account disabled in Jive?
Since the old user account in the LDAP system is disabled/deleted, Jive correctly disables the associated user account in the Jive instance. This works as expected and designed.
Why is a new account created in Jive?
Since the new account in the LDAP system has a different unique user identifier, Jive correctly considers it to be a different user. Computer systems recognize different user accounts using unique identifiers since there can be two people with the same names but not the same unique identifiers.
What can I do to change this behavior?
It is recommended that you look into the possibility of changing the existing user's details in your LDAP system and not disabling/deleting it and then recreating a new user account.