spring-projects / spring-projects/spring-security
Improve OAuth2 Device Authorization consent handling for missing scopes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
There are two related issues in the OAuth2 Device Authorization flow when no scopes are requested.
The first issue is that when a device_authorization request is made without a scope, everything works fine, but when both authorities and scope are empty, an error is thrown that does not comply with Section 3.3 of RFC-6749. The second issue is that the error itself is reported as a client_id error rather than a scope error. Therefore, we need to resolve these two issues.
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
The entry point is the OAuth2 Device Authorization flow's device_authorization request; first compare its no-scope handling with RFC-6749 Section 3.3. Verify that empty authorities and scope produce a scope error rather than a client_id error, and confirm both behaviors against the linked pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, authorization, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100