spring-projects / spring-projects/spring-security
Customizable OAuth2AuthorizationCodeGrantFilter
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Expected Behavior
when the filter succeeds, the user should be able to customize the behavior.
Current Behavior
when the OAuth2AuthorizationCodeGrantFilter succeeds or fails, the DefaultRedirectStrategy is used for both success or failure.
I think a classic successHandler / failureHandler would be ideal.
Spring Security 7.1 M3
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 locating OAuth2AuthorizationCodeGrantFilter and tracing its success and failure paths to see where DefaultRedirectStrategy is used. The work is done when those outcomes can be customized independently and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100