Getting "Unauthorized; scope does not match" after refreshing an OAuth2 token

Guy Schlider
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 4, 2024

Hi,

 

We see a very weird behavior since last week, where after refreshing an access token and trying to create a new issue - we get 401 error: "Unauthorized; scope does not match"

The strange thing here is that after a few minutes - the same token (result of the refresh token) is working for the same request. 

any ideas?

1 answer

1 vote
Einar Pehrson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 6, 2024

Hi @Guy Schlider

Support for lenient URL path processing for OAuth 2.0 requests is being removed. Roll-out is currently at 50%.

Please see the removal notice and the deprecation notice for more details.

If you are unable to find to troubleshoot your specific case, please submit a Developer Support request.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events