-
Suggestion
-
Resolution: Won't Do
-
None
-
None
Allow users to use a common identity and authentication system to gain access to HipChat services. Web and chat (XMPP.)
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use HipChat so we can continue improving your experience.
We are offer existing this feature to HipChat Plus Cloud customers as a private beta. If you are interested in joining the beta, please sign up here. We'll alert you when the beta is available for your group.
HipChat Server now has SAML/SSO support, for details please see HCPUB-524.
We will continue to update this and the other top voted issues here in our public issues tracker, so please watch this issue and you'll be notified about future updates.
Please remember that your suggestions on jira.atlassian.com are one of many inputs for the HipChat roadmap.
You can learn more about our process here.
We thank you for your feedback, and will continue to listen to you and all our customers to better understand your needs.
Regards,
The HipChat Team
- duplicates
-
- Closed
- is related to
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page
Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
[HCPUB-317] Single Sign On (SSO)
I am very troubled by the fact that we now have to create passwords for all of our JIRA/Confluence Cloud users if we want to still be able to use HipChat. All of our users use Google Apps OAuth to sign in and now cannot sign in to HipChat because of that. Bad job, Atlassian.
SSO with GSuite for HIpChat Cloud please.
This is really confusing our users and not sure how this change happened without the SSO for GSuite .
PLease help us make it easier for our users.
Thank you,
We'd like SSO with Azure AD for hipchat native mobile just as you do for web.
Aaron Lynn
added a comment - We'd like to see SSO with GSuite for HipChat Cloud.
As with I imagine a lot of other companies, we started using Confluence and JIRA first and then signed up for HipChat.
Now that HipChat uses Atlassian IDs to sign in, we've had to come up all sorts of workarounds for signing in - why is it that we can go to JIRA/Confluence and click "Sign in with Google" (with no password), but then when we sign into the same account in HipChat we have to create a password for the very same Atlassian account?
Aaron Lynn
added a comment - We'd like to see SSO with GSuite for HipChat Cloud.
As with I imagine a lot of other companies, we started using Confluence and JIRA first and then signed up for HipChat.
Now that HipChat uses Atlassian IDs to sign in, we've had to come up all sorts of workarounds for signing in - why is it that we can go to JIRA/Confluence and click "Sign in with Google" (with no password), but then when we sign into the same account in HipChat we have to create a password for the very same Atlassian account? Do you know when the SAML feature will be available to HipChat Plus cloud instances?
Extremely interested in this beta as we run the full Atlassian stack and SAML is something we have been waiting for years.
Richard VandenBosch
added a comment - Add me to the beta. Without SAML 2.0 / MFA (OKTA) HipChat server is blocked for us.
Richard VandenBosch
added a comment - Add me to the beta. Without SAML 2.0 / MFA (OKTA) HipChat server is blocked for us. 
Aaron Matthews
added a comment - Complete blocker to using hipchat – slack offers this.
We recently announced that we would be discontinuing our team messaging tools, Stride and Hipchat, and will therefore be closing out all related feature requests and open issues. The end of life date for Stride and Hipchat Cloud is February 15, 2019. Until that time, we will only issue product updates for security issues or critical bugs.
If you are an existing Hipchat Server or Data Center customer and feel like this issue has been closed in error, please contact support to let us know.
Our recommended migration path is to Slack - you can read more about this and other options at Stride and Hipchat Cloud End of Life: Just over 90 days
Thank you for your input on this ticket and for being a valued Atlassian customer.