API tokens without scopes are being "deprecated" #865
Unanswered
Thomascountz
asked this question in
General
Replies: 1 comment
-
|
I set this up a couple weeks ago at a new job and I tried to create a scoped token with a couple of different classic scopes. (edit repo, something else) and they failed. I eventually reverted to an unscoped token which works. It would be good to figure out a working scope set. There should be a documentation bug once this is done to update the install instructions to use a new scoped token. The developer docs should also push to use a scoped token so when someone needs more permission they hit the issue and update things accordingly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This banner recently appeared on the API creation page (linked to from the README), but there doesn't appear to be any other public announcement, see: https://community.developer.atlassian.com/t/api-tokens-without-scopes-are-being-deprecated/92510
That said, I think it would be good to recommend users create tokens with scopes.
I wonder if any of the classic scopes would be sufficient. There are over 150 fine-grained scopes for Jira alone.
Beta Was this translation helpful? Give feedback.
All reactions