Support HipChat Connect

Issue #30 open
Alex Wei created an issue

Comments (8)

  1. Alex Wei reporter

    @naderghanbari Unfortunately that's an internal page.

    Here are some of the main differences:

    • descriptor format (HipChat connect is very different, see https://www.hipchat.com/docs/apiv2/capabilities)
    • HipChat allows plugin on a global level (requires admin permissions) and one a room level (doesn't require admin permissions)
    • authentication (HipChat Connect's JWT authentication is a standard one, which is less secure than the Atlassian-customised one used in AC)

    It's possible to support JIRA/Confluence and HipChat at the same time, but ac-play-scala needs to be forked or with the capabilities of handling HipChat being added.

    There is a spike branch: https://bitbucket.org/atlassianlabs/atlassian-connect-play-scala/branch/issue/hipchat and the related shipit project: https://bitbucket.org/atlassianlabs/whoslooking-connect-scala/branch/hipchat.

    As you can see from the code, they are not aligned in the database record schema or jwt handling. Additionally, we can't match jira user with hipchat user, and have to resort to checking the equality of the email address, which may not always be the same.

  2. Nader Hadji Ghanbari

    Hey @AlexWei ,

    Thanks for the reply. We (the team) went through the docs to understand the differences. Most probably we will do what you mentioned above, creating a framework for HipChat connect (so far we gave it a try with Play 2.5 and everything seems ok). Hopefully we can open source it soon.

  3. Log in to comment