Uploaded image for project: 'HipChat'
  1. HipChat
  2. HCPUB-858

Provide an option to log in to HipChat Server using the username instead of email.

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Other
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Status as of 28 September, 2017

      Hello!

      We are reviewing the user management experience as a whole.

      As we get closer to what the new experience looks like, we will post updates here. In the meanwhile, if you have specific requirements, please comment and let us know here.

      Thank you,
      The HipChat Data Center team.

      Problem

      We have integrated our Hip-chat to crowd. We created a delegated directory in Crowd dedicated for Hipchat only. This is allowing our users to authenticate against our AD.

      Currently, Hip-chat log in page asking for email address for login, instead of username, unlike all other Atlassain applications. This is confusing for our usersas they are using their NT username for their authentication in all other Aastlassain application we have including JIRA, Confluence,Stash,Bamboo,Fe-Cru etc

      Suggested Solution

      Provide the option for users to log in using their usernames instead of email addresses.

      Workarounds

      None at this time

            [HCPUB-858] Provide an option to log in to HipChat Server using the username instead of email.

            carsimadmin added a comment -

            Same as Michael Rudel on all points. Having the login to HipChat be different than the login to jira/confluence is confusing to users and makes it look like a disjointed product. 

            carsimadmin added a comment - Same as Michael Rudel on all points. Having the login to HipChat be different than the login to jira/confluence is confusing to users and makes it look like a disjointed product. 

            Michael Rudel added a comment - - edited

            This is super confusing for our users, because we authenticate against our own LDAP directory not tied to the corporate AD... but we use the corporate AD/e-mail addresses as the e-mai" attribute for automated password resets tied to their employment.

            So our users have to log in to 98% of applications using one username and password - but since this one is their corporate e-mail address, they become confused and use their corporate credentials.

            70% of the reason we chose HipChat is because of LDAP integration, it would be great if it was consistent with all of the other applications in the suite.

            Michael Rudel added a comment - - edited This is super confusing for our users, because we authenticate against our own LDAP directory not tied to the corporate AD... but we use the corporate AD/e-mail addresses as the e-mai" attribute for automated password resets tied to their employment. So our users have to log in to 98% of applications using one username and password - but since this one is their corporate e-mail address, they become confused and use their corporate credentials. 70% of the reason we chose HipChat is because of LDAP integration, it would be great if it was consistent with all of the other applications in the suite.

              Unassigned Unassigned
              kbaxley Kent Baxley
              Archiver:
              mandreacchio Michael Andreacchio

                Created:
                Updated:
                Resolved:
                Archived: