Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Writing hipchat client: HipChat Authentication

I am prototyping HipChat client and I'm stuck at building good authentication experience. I would like to implement similar authentication dialog as HipChat clients built by Atlassian provide. There is no need to generate auth tokens/etc, you just type email/password and client is able to obtain oauth token.

How do they do? Clients use as client_name in request to


Question that I have: how do I register my own client? If I use any random name I get "Named OAuthClient not found <name>".

How to register client name that will work with any HipChat server, including

2 answers

+1 on wanting this type of global auth flow. Slack offers it with their OAuth2 flow and doesn't require a per group integration install and secret.

Without this, it means we won't be integrating with HipChat auth in our product. It's too much to expect users to install an integration up front. It's not the seamless experience we are trying to deliver.

1 vote
rich Atlassian Team Dec 17, 2015

This is currently not possible. The flow you described with the oauth id is used internally inside our new desktop and mobile clients. The only other way to obtain an access token via a 3-legged oauth flow is to create an add-on that you have to require a HipChat customer to install. Our OAuth tokens are scoped by group. We don't have allow global tokens. Sorry about that.

thanks for the answer. are there any plans to allow creating own named oauth clients? I was willing to write hipchat client for windows phone (existing ones kind of suck, 3-legged auth is the biggest issue), but this makes writing nice auth experience impossible. and I guess I can't use in my client :(

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events