Login part of script fails (jira backup Client must be authenticated to access this resource)

[Former user]

As of 21.10.2016 the login part of the script seems to fail - Atlassian might have changed something here?

[24-10-2016 12:13:56]: Attempt 1: Trying to initiate JIRA Cloud Backup. <?xml version="1.0" encoding="UTF-8" standalone="yes"?><status><status-code>401</status-code><message>Client must be authenticated to access this resource.</message></status>

[Waldemar Müller]

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><status><status-code>401</status-code><message>Client must be authenticated to access this resource.</message></status>

is the content of $BKPMSG at that time

Grabs cookies and generates the backup on the UI --> This is the part that fails, authentication and download at the end of the script still works

[Martin Gonzalez Adolfi]

Exactly the same behaviour here.

[Eugene Chernov]

Any achievements, guys? Still can't figure it out...

[Frank Wong]

Same error here. Backups were working just fine until Oct 22nd and then broke with the same error message above. I assume either the REST method changed or the token format changed. I could not find any documentation anywhere.

Just found a workaround (or fix). Seems token is no longer valid or deprecated. Just remove the cookie parameter and pass the user:password like:

curl -u <user>:<password> --header "X-Atlassian-Token: no-check" -H "X-Requested-With: XMLHttpRequest" -H "Content-Type: application/json" -X POST https://<site>.atlassian.net/rest/obm/1.0/runbackup -d '{"cbAttachments":"true" }'

[Mike Barmettler]

Hi guys,

see Antony's helpful post here: https://bitbucket.org/atlassianlabs/automatic-cloud-backup/issues/3/atlassian-are-changing-the-way-that-they

hth

[Dario B]

New Jira shell scripts available