We have a local HipChat instance integrated with our LDAP server. We have changed the email on one user and now that user cannot authenticate; the new email address does not propagate down to HipChat even after syncing LDAP. Deleting the "old" user record in HipChat does not help.
Is there a way to reliably sync updated emails from LDAP to HipChat, or delete this old user?
Some older versions (read v1.3.1 and below) had some issues with changes in LDAP correctly updating the HipChat Server database. If you're on v1.3.1 or below, we strongly suggest updating to v1.3.4 prod to help combat these issues. Upgrading HipChat Server and HipChat Server Release Notes are useful links.
If you're on v1.3.4 prod and are still experiencing this, you can try disabling the integration: HipChat user interface -> Server admin -> Directory > 'disable'. Wait a few minutes and then 'enable' it. This will force a full sync and it should pick up the changes.
If that still doesn't help, please reach out to our support team to help: firstname.lastname@example.org or file a ticket at support.atlassian.com.
HipChat Server Support Engineer | Atlassian
Per this documentation , HipChat should periodically synchronize the changed credentials. Maybe these links will help :
...from the beginning. We have built up a lot of content in HipChat, with it being a core tool in our distributed company model. While it is true that we didn’t need to move to Slack immediately, we felt it...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs