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

How can I get my Hipchat Integration on Heroku to authenticate?

Matt Rowe February 23, 2017

I followed the step-by-step guide here.

I made a simple app that posts a message to the rooms the Integration is installed on per a regex (as described in the tutorial above).

When I initially add the Integration to a hipchat room, it works fine. However, after a period of time it stops working.

The following error appears in my Heroku logs:

JWT verification error: 400 Request can't be verified without an OAuth secret

I assume something with my configuration is wrong or my lack-of-use-of-OAuth, but after googling around I can't find any specific answers on what it should look like.

My config.json looks like this:

"production": {
    "usePublicKey": true,
    "port": "$PORT",
    "store": {
        "adapter": "jugglingdb",
        "type": "sqlite3",
        "database": "store.db"
    },
    "whitelist": [
        "*.hipchat.com"
    ]
},


And my request handler looks like this:

app.post('/foo',
    addon.authenticate(),
    function (req, res) {
      hipchat.sendMessage(req.clientInfo, req.identity.roomId, 'bar')
        .then(function (data) {
          res.sendStatus(200);
        });
    }
);

Any specific direction on configuration and use of Oauth for Hipchat and Heroku would be amazing!

Stack Overflow link.


1 answer

1 vote
Matt Rowe March 3, 2017

Three things I needed to do in order to fix my problem:

  1. Install the Heroku Redis add-on for my Heroku App. (confirm that the Environment Variable for ($REDIS_URL) was added to your app settings).
  2. Add this line to my app.js file:

    ac.store.register('redis', require('atlassian-connect-express-redis'));

  3. Change the production.store object in the config.json to be the following:

    "store": { "adapter": "redis", "url": "$REDIS_URL" },

crivers
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 3, 2017

Thanks for posting the answer... hopefully it helps out other dev who might encounter the same stumbling block in the future!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events