Authenticating OAuth 2.0 for outgoing web requests in Jira Automation rules
Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Solution
You'll need two specific outgoing web requests to authenticate over OAuth- the first request will generate a token that's used in the second request in order to obtain the credentials needed for subsequent web requests.
First request
Common values for the Content-Type header are application/x-www-form-urlencoded ( shown below ) or application/json
Second request
Set the value for the Authorization header to Bearer {{webhookResponse.body.access_token}} as shown below. You may need to include additional values in the form body as well.
Values provided in the webhook body are not HTML URL encoded. If a value contains a special character, $ for example, it is sent as-is instead of its HTML URL encoded equivalent of %24. If authentication is failing unexpectedly, convert special characters in values to their HTML URL encoded equivalent