How on earth are the new API tokens with scopes meant to be used?

[Longfei Huang]

I used to create api token by clicking "Create API token" to create Jira issues and it has been working well for me .

But when I saw the notice, I tried switching to 'Create API token with scopes'. However, it didn’t work for me. I’ve already set all the required permissions as mentioned in the documentation

I just got the error message like 

So what should I do to fix this ? @Mohanraj Thangamuthu 

[Mohanraj Thangamuthu · Accepted solution]

Hello, Good day. I would like to know if you are impacted with the following bug. https://jira.atlassian.com/browse/JRACLOUD-94545?

Let me know if your issue is different. Thanks

[Longfei Huang]

Yes, thanks. That's exactly what I needed. I think the document should be updated promptly whenever the function changes, otherwise it will cause confusion.

[marc -Collabello--Phase Locked-]

The new tokens with scopes are another type of API token, and unfortunately Atlassian failed to provide documentation on how to use them and what the difference with the old ones is.

The scoped tokens are OAuth tokens and use different API endpoints than the unscoped tokens, see https://developer.atlassian.com/cloud/oauth/getting-started/making-calls-to-api/ .

[Longfei Huang]

Yes, I read the documentation too. But after going through it, I realized it's mostly about OAuth2, not basic auth. Also, it requires a cloud ID, which I haven’t been able to get.

So basically, the official side wants to deprecate the original API tokens even though the documentation isn’t ready yet. That’s really too hasty.

[Jens]

You can get the site ID (also known as cloud ID or Tenant ID) like this: https://<my-site-name>.atlassian.net/_edge/tenant_info.

[Andrea Robbins]

so as long as we use the scoped token with the right endpoint, we can still use basic auth? 

[Andrea Robbins]

Also curious if the token works for JSM endpoints, I just see Jira and Confluence