Writing hipchat client: HipChat Authentication

[vmg]

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 com.atlassian.hipchat.win-clients as client_name in request to https://www.hipchat.com/users/authorize.

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 hipchat.com?

[Sean Johnson]

+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.

[rich]

This is currently not possible. The flow you described with the com.atlassian.hipchat.win-clients 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.

[vmg]

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 com.atlassian.hipchat.win-clients in my client :(