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

Guy Schlider

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?

Einar Pehrson

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.