I have followed the following documentation to the letter:
I cannot get the token to work for viewing a request (e.g. a GET to "https://mybusiness.atlassian.net/rest/api/2/issue/ticketid"). I have completed the following steps to attempt to resolve:
I have exhausted troubleshooting options and the only thing I can think of is that perhaps the fact that we have SAML active on our account is causing problems with the API tokens? (SAML has caused weird issues for us in other areas before.)
Screenshot of a successful query from a browser plugin while logged into the associated Jira account in a different tab in Chrome. This fails with a 404 if I make the same query after logging out in the other tab (i.e. without the associated login cookie active in the browser).
Thanks for using Atlassian Community.
Apitokens shouldn't be affected by your team's implementation of SAML. With or without SAML, apitokens are used to authorized API calls into Jira cloud via Basic Authentication.
To use that, you will need to add an authorization to your rest call.
The username will be your email address and the password is the apitoken string. Talented will convert that for you into the proper Authorization header which will be sent out with the rest call.
I hope this helps.
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