Details
-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
HCS 1.4.1, HCS 1.4.3, HCS 2.0.4, HCS 2.0.6, HCS 2.2.3, HCS 2.2.4
-
Severity 2 - Major
Description
Directory user will switch to become internal user if admin deactivates and reactivates the account directly within HipChat Server
Environment
- HipChat Server 1.4.1
- HipChat Server 1.4.3
- HipChat Server 2.0.4
- HipChat Server 2.0.6
- HipChat Server 2.2.3
- HipChat Server 2.2.4
Steps to Reproduce
- Integrate HipChat Server with LDAP server
- Run synchronisation and LDAP users will be copied over to HipChat Server
- As an admin, manually deactivate a user that has been synchronised directly from HipChat Server (Group admin > Users > Select the user > Deactivate)
- Reactivate the user within the HipChat Server Web UI under "Users"
Results
The directory user that has been deactivated and reactivated will become local user. There is a way to double check this through a value in the database. Contact support for more info.
The impact of this is that directory user will no longer able to login to HipChat with directory password as the account is switched to local account.
Workaround
There's a workaround to map the local user back to directory user. Contact support for more info.
Notes
- Admin should avoid deactivating and reactivating directory user accounts directly from HipChat Server and do this directly from the LDAP server instead. The deactivation and reactivation will then be propagated to HipChat Server after a successful synchronisation.
- Directory users should not manually deactivate their accounts from https://<server-url>/account/deactivate but instead contact the admin to do that directly from the LDAP server.