Authorize does not support scope/permissions
Open
Nobody has claimed this yet.
api
enhancement
- Dominant language
- Go
- Stars
- 323
- Forks
- 133
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 2
Description
This is a feature request.
I would like to be able to use the /authorize endpoint to generate an access_token with a particular scope. As a minimum, I'd like to at least lock it down by team.
Read-only access and site-level access would also be preferred.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the /authorize endpoint in the Open API specification and the surrounding authentication definitions. Clarify how team, read-only, and site-level permissions should be represented and how the resulting access_token should enforce them; the issue is done when the agreed scope behavior is specified consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100