HipChat authentication failure after email change

[John Karabaic]

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?

Thanks,

jk

[David Maye · Accepted solution]

Hi John,

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: server-support@hipchat.com or file a ticket at support.atlassian.com.

Cheers,
-David
HipChat Server Support Engineer | Atlassian

[John Karabaic]

I upgraded to v1.3.4, resynced LDAP, and it started working. Thanks for your help. You guys are awesome. Good luck on the IPO!

[Yagnesh Bhat]

Per this documentation , HipChat should periodically synchronize the changed credentials. Maybe these links  will help :

https://confluence.atlassian.com/hc/connecting-to-an-ldap-directory-687218283.html

https://confluence.atlassian.com/hc/configuring-user-directories-686856978.html