Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Integration of HipChat in Confluence fails

Jan-Peter Rusch
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 3, 2014

Hi all,

I'm trying to connect our local hipchat beta server (1.0.6) to our Confluence system.

I generated API v1 admin & v2 tokens, validated both of them with a rest client using:

https://ourhipchatserver.local/v2/room?auth_token=xxx

and

https://ourhipchatserver.local/v1/rooms/list?auth_token=yyy

Both requests return a valid list of rooms.

Entering the hipchat base url to Confluence (I gues it should be https://ourhipchatserver.local) and pasting the working tokens in the Admin Token field leads to:

Your HipChat Auth Token appears to be invalid

I configured ssl on hipchat to use our local CA. All servers (Hipchat, Confluence, Jira) use the same CA.

Any hints? What am I doing wrong?

Thx,

Jan

2 answers

0 votes
David Maye
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 12, 2014

Hi Jan-Peter,

I've already responded to your support inquiry, however for others having the same issue, it appears to be a bug in the beta. We have filed a bug ticket against it and the developers are currently investigating. Once we fix it, we'll apply the fix in the next upgrade. You can 'watch' the release notes page to receive any updates whenever a new update is posted.

Thanks to everyone who is participating in the beta!

Cheers,
-David 

0 votes
Patrice Rompas
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 7, 2014

Hi Jan,

Few things to check:

  • The API v1 token will be 30 characters long, not 40 characters long (which is an API v2 token). As far as I know, the integration takes the v1 token.

  • The base URL must be your FQDN, not api.hipchat.com.

  • The two systems (HCS and Confluence) must be able to communicate between each other. This means that the correct ports must be opened for both (typically 443 TCP if the Confluence server is offsite).

Otherwise, create a support ticket in HipChat Support along with the screenshot of the HipChat add-on configuration screen in Confluence

All the best,
Sam 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events