I have below details with me:-
3.Correct User Name
4.Rest API :- rest/api/3/project(to see all the projects)
Used Authorization as Basic Auth and username as email address and password as the API token key.
I hit this api via Postman and i am getting error as :-
Basic authentication with passwords is deprecated. For more information, see: https://confluence.atlassian.com/cloud/deprecation-of-basic-authentication-with-passwords-for-jira-and-confluence-apis-972355348.html
Please suggest what am i missing here.
Postman automatically add the Authorization header for you with your basic authentication email:apiKey based64 encoded , when I mention my issue for some reason my Postman was keeping my old header instead of update with my new credential.
Also I've just checked that if your apiKey is not correct you will receive the same error "Basic authentication with passwords is deprecated", can you generate a new api key and try it again updating your password with the new generated key?
Here are the instructions to generate a new key:
If you have Linux you can check by running this command:
curl -v https://mysite.atlassian.net/rest/api/3/project --user email@example.com:my-api-token
I am experiencing the exact same issue, same commands worked fine last month. Today not working.
I generated a new API key, same result.
curl -u $EMAIL$:$API KEY$ -X DELETE -H "Content-Type: application/json" https://XXX.atlassian.net/rest/api/3/group/user?groupname=jira-software-users\&\accountId=$ACCOUNT ID$ && echo done1 &
i am so sorry to "revive" this thread. But i am trying to connect to the rest API via Zapier, with a custom Webhook and i get the same error message. I am doing it as @Italo Qualisoni [e-Core] described in his first reply:
"Your username should be only your email and the password will be API Token."
i also generated a new Api Token - but same result.
Any ideas on what i can do?
thanks in advance guys ^^
Hey @Hürkan Utan ,
This happens when your authorization isn't set properly.
I recommend to test your API Token in Postman first and once you can confirm the token is working, I recommend you to move to Zapier.
In Postman you can use the basic authentication, with your mail as username and token as password (same as my screenshot in previous threads)
Let us know if your token works in Postman, you can test using the below endpoint to check the status of your site.
I tested as you said - first in Postman and i used basic auth. in Postman and i successfully could change the summary. Following are some screenshots :)
the original Summary was "Test" and now its changed.
And the API key seems to be working just fine.
Now i want to change the approver of the Ticket. Should i test it in Postman first as well? If so how do is search for the field because the customfield i had originally is not working.
Soo i searched in the Raw data and found that custom field
customfield_10003 - actually sets the approver but when i trx to change it with the another ID i get this error:
Thanks for all your Help @Italo Qualisoni [e-Core] ^^
sooo to update the Zap worked ^^
thanks for your Help - additionally i tried to configure the Basic auth in Zapier, which
did not work. However when i copied the Authorization header from Postman it did
function as intended :)
now i just need to figure out how to move the issue to another state ^^
Thanks and Cheers
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events