Jira API fails auth in automation but succeeds in Postman

[Erica Robinson]

Hey all,

I'm currently attempting to build out an automation that will do the following:

1. Run through the Get Projects Paginated API
2. Create a variable with the Projects' ID
3. If the variable isn't empty, run through the Get Project Components API 
4. Email me with the list of components for the projects

Reason: I've been tasked to get a list of all components across all of our projects (~60) in a cleanup effort.

Right now, I'm stuck at the first API call. I've confirmed the call works just fine in postman, I get a list of projects back, no problem. The second API also works, but if I don't include the project ID, I have no way of telling what component belongs where - thus the automation.

The automation is failing with this error noted in the webhookResponse:

X-Seraph-Loginreason=[AUTHENTICATED_FAILED]

I've tried the following combinations

Key	Value
Authorization	Basic <email>:<API token>
Authorization	Basic <email>:<Base64 encoded token - API token only>
Authorization	Basic <Base64 encoded token - email + API token>
Authorization	Basic <API token>
Authorization	<API token>
Authorization	<Base64 encoded token - email + API token>

I've also tried adding in - recommended from the Atlassian AI:

X-Atlassian-Token

no-check

None of these modifications have worked or changed the output - other than just failing the test checks immediately vs just in the webhookResponse body.

Here's the piece of the automation that's failing with the audit logs:



Here's the postman call using the basic auth creds:

[Bill Sheboy · Accepted solution]

Hi @Erica Robinson 

Did you try only sending the Authorization header and encoding the value passed for the token as described in this article:

https://community.atlassian.com/forums/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Kind regards,
Bill

[Erica Robinson]

Hey @Bill Sheboy

I just tried that modification and the results were unfortunately same:

[Bill Sheboy]

From inside the rule editor for the Send Web Request action, when you select the "Validate your web request configuration" at the bottom to run the call, what do you observe?

And, what are the permissions of the user for which the API token was created?

[Erica Robinson]

When I select the "Validate your web request configuration" it responds with a 200 success; however when I look at the headers it provides the auth failure there as well:

I can confirm that the request is also passing the base 64 token:

Since it's my API key, it has Org Admin + Jira Admin permissions. I have access to everything in our Atlassian org.

[Bill Sheboy]

Okay, let's try this...

Automation rules can get "glitched" by too many edit / publish cycles.  This breaks them behind the scenes, causing weird symptoms and errors.  The way to check for that cause is:

• disable this rule
• create a new one from scratch, entering just the minimum information to call your REST API endpoint call
• test the rule
• if that works, delete the original rule when it is no longer needed as a reference

In my experience, the root causes of this behavior are when rules save, they do not consistently remove information which is no longer needed (such as in the Send Web Request settings).  This can also happen for rules which are imported with invalid connection information, such as to Slack, Confluence, etc.

[Erica Robinson]

Hey Bill,

I've following the steps you outlined and rebuilt the rule with just the webhook. Unfortunately it's still failing here :(

[Bill Sheboy]

Thanks for trying that, Erica. 

After a bit of digging, I found a related JAC defect / suggestion for this symptom indicating a problem with the API token...and a misleading error message problem: https://jira.atlassian.com/browse/JRACLOUD-82932

So, the only other two suggestions I have are:

• create a new API token, encode it for the authorization, and try with the new value
• and if that does not work, work with your Jira Product Admin to submit a ticket to Atlassian Support to take a look: https://support.atlassian.com/contact#/

If you end up submitting a ticket to support, please post what you learn from them to benefit the community.  Thanks!

[Erica Robinson]

Hey Bill,

A brand new token with the same permissions (no scope configured) worked perfectly! Thank you again for your help with this one. :)