ERROR - {"message":"Client must be authenticated to access this resource.","status-code":401}

[Marcelo Riveiro]

We were using this script to make BACKUP from linux, but about 1 month ago it fails with these error:

{"message":"Client must be authenticated to access this resource.","status-code":401}

(PART OF SCRIPT)

COOKIE_FILE_LOCATION=jiracookie
curl --silent --cookie-jar $COOKIE_FILE_LOCATION -X POST "https://${INSTANCE}/rest/auth/1/session" -d "{\"username\": \"$USERNAME\", \"password\": \"$PASSWORD\"}" -H 'Content-Type: application/json' --output /dev/null

BKPMSG=$(curl -s --cookie $COOKIE_FILE_LOCATION -H "Accept: application/json" -H "Content-Type: application/json" https://${INSTANCE}/rest/backup/1/export/runbackup --data-binary '{"cbAttachments":"true"}' )

Can you help me?

[edwin · Accepted solution]

Hi @Marcelo Riveiro ,

Authentication with username and password is deprecated. You'll have to create and use API tokens

Deprecation notice - Basic authentication with passwords and cookie-based authentication

[Marcelo Riveiro]

Thanks for the response and help.

[Chintan S Soni]

I changed my way to call API and now i am using token instead of password. But still i am getting 401 issue "Client must be authenticated to access this resource".

[Thomas Fozzi]

Try like this:

1) encode the string

"username:password" 

with Base64

2) add the header

"Authorization: Basic <encoded string>" 

to your cUrl command

[marcelo]

This works for me, thanks Thomaz.

[marcelo]

Actually works just for one account, the other account that seems to have the same permissions i get 401 again, using token also.

[Thomas Fozzi]

Have you tried loggin to Jira on the browser with the second account, using exactly the same username and password you're using on cUrl?

Also consider that in case you change the password you must regenerate the API token.

Thomas

[marcelo]

Thanks Thomas, you're right, it was my mistake changing the token id's between all accounts.

[Karl Samson]

Hi, we are using Tokens and Crowd to authenticate Username and password, basically semi SSO sign in, and we are getting this same error message when we try to project a Big Picture schedule Gadget on a Confluence page!? Any ideas on how to fix this would be greatly appreciated!!

[Alec Jasanovsky]

Also experiencing this issue - even though i'm using a token. 

[ji wenhao]

Just like what @Chintan S Soni said, I found the same problem when I call API by using api token without password. Please do me a favor!

[Karl Samson]

Moved to latest thread!

[David Witkowski]

Same issue here!

[Marcelo Riveiro]

This way it is working

BKPMSG=$(curl -s -u ${USERNAME}:${API_TOKEN} -H "Accept: application/json" -H "Content-Type: application/json" --data-binary '{"cbAttachments":"true"}' -X POST https://${INSTANCE}/rest/backup/1/export/runbackup )