How do OAuth scopes work with the coaz model?
Open
Nobody has claimed this yet.
coaz
- Dominant language
- TypeScript
- Stars
- 160
- Forks
- 41
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 23
Description
From @maxwellgerber:
Oh, how do classic OAuth scopes work in this model? If a user wants to give client A read write access and client B read access, how does that get encoded into the SARC representation? Is that still evaluated by the PDP?
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
No files or tests are named. Start by reading the existing SARC representation and PDP behavior, then trace how OAuth scopes could express different read/write access for clients A and B. Done means documenting whether classic OAuth scopes are supported, how they are encoded, and whether the PDP evaluates them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100