I've written a python scrips to get multiple jira fields (after authenticating with user:api/password) which then passes to a jenkins job, It started failing yesterday and I came across this link https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/
it says the use of username/key is no longer supported instead we should use account ID,
But I am unable to find a method to authenticate with account ID,
say if I'm using the below method to post a comment to a ticket via api/2, how do I do the same with api/3 by using the new method as accountid ?
curl -D- -u 'test@yourdomain.com:password' -v -H "Content-Type: application/json" --data '{"body":"hi"}' https://yourdomain.atlassian.net/rest/api/2/issue/$issue/comment
Hi,
I suppose this relates to the same issue as https://community.atlassian.com/t5/Questions/JIRA-Rest-API-authentication-always-returns-401-unauthorized/qaq-p/1110047.
Thanks, yes it was.. I was using basic instead of api toke, it works with api token in api/2 itself, But going forward how do I achieve the same with api/3 and accountid combination ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.