-
Bug
-
Resolution: Fixed
-
High
-
4
-
Minor
-
-
Warranty
Issue Summary
The Get valid project key (https://api.atlassian.com/ex/jira/<cloudid>/rest/api/3/projectvalidate/validProjectKey?key=TEST) API does not work with API tokens that have scopes
Steps to Reproduce
- Create an API Token with READ Jira scopes
- Use the API token with the Get valid project key API:
curl --request GET I am running a few minutes late; my previous meeting is running over. --url 'https://api.atlassian.com/ex/jira/99abc88abc-1234-cdef-4567-8899f-999abcde/rest/api/3/projectvalidate/validProjectKey?key=TEST' \ --user 'email@domain.com:xxxxxxxxxxxxxxxx' \ --header 'Accept: application/json'
Expected Results
"STAR1"
Actual Results
The below exception is thrown by CloudFront:
{"code":401,"message":"Unauthorized; scope does not match"}
- The API does not require any permissions.
Workaround
- Use the Validate project key
- Use non-scoped API tokens for the time being.
- relates to
-
CLOUD-12617 Add support for atlassian.net when sending web requests with scoped API tokens to avoid permission errors
- Gathering Interest