Why am I not able to use GenieKey with NewRelicV2 integration?

[christian_steiner]

Hi,

We are about to integrate NewRelic into JSM OpsGenie for alarming.

For that we are going to use a OpsGenie Integration (NewRelic).

The setup was pretty simple and first tests were successful.
I just took the connection string provided by OpsGenie, pasted it into NewRelic's destination and it worked.

Then I wanted to make it a bit more secure by removing the "APIKey" from the URL and having it in the Header instead.

So I tried the following:

URL: https://api.atlassian.com/jsm/ops/integration/v1/json/integrations/webhooks/newrelicv2
Header: Authorization: GenieKey ########-####-####-####-############

Where "GenieKey" = "ApiKey"

This always gives me an unauthorized 401 response.

I do not understand why...
Is it not possible to use Authorization header with NewRelic integration?
Am I doing something wrong?

BTW: I was already able to bring a standard REST API integration to work with header and GenieKey.

Thanks for your help.

BR.

[Bruna Silva · Accepted solution]

Hello @christian_steiner,

Thank you for reaching out to Atlassian Community!

Currently, it's not possible to remove the API key from the URL, but we have an open feature request asking for this ability, as you can see below:

• As a Opsgenie admin I would like to move apiKey in URL to request headers for security reasons

Please, feel free to click on "Vote for this issue" and add yourself as a watcher to be kept informed about the state of the feature moving forward.