When username is changed in LDAP or Crowd, the user is deactivated in Hipchat Data Center

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Low
    • None
    • Affects Version/s: None
    • None
    • Severity 2 - Major

      Summary

      If a user's username is updated in LDAP or Crowd and a manual sync is run, the user will be deactivated from Hipchat Server/Data Center.

      Environment

      • Hipchat Data Center 3.1.1

        This is not an issue in Hipchat Server

      Steps to Reproduce

      1. Connect Hipchat to an external user directory
      2. Sync a few users over
      3. Update the directory username for one user

      Expected Results

      • The user should still be active and allowed to login
      • The username should be updated in the internal (Crowd) cwd_user and (Hipchat) users tables

      Actual Results

      • The user is deactivated from Hipchat
      • The username is updated in the (Crowd) cwd_user table
      • The username is not updated in the (Hipchat) users table

      Workaround

      As soon as you make a change to usernames or map the username in Crowd to a new LDAP attribute. Run a Disable/Enable from the directory page in Hipchat.

            Assignee:
            Unassigned
            Reporter:
            Arbi Dridi
            Archiver:
            Michael Andreacchio

              Created:
              Updated:
              Resolved:
              Archived: