spring-projects / spring-projects/spring-security
Support 303 status for authorization response
Open
Nobody has claimed this yet.
in: oauth2
type: breaks-passivity
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Expected Behavior
According to A comprehensive formal security analysis of OAuth 2.0. 303 redirect should be used to drop the body of an HTTP POST request.
Current Behavior
DefaultRedirectStrategy in OAuth2AuthorizationEndpointFilter sets the status to 302
Context
If needed, i can work on it.
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 at DefaultRedirectStrategy in OAuth2AuthorizationEndpointFilter and inspect how the authorization response selects status 302. Confirm the intended 303 behavior for POST requests and verify the authorization endpoint tests cover the resulting response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authorization, backend, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100