spring-projects / spring-projects/spring-security
Make OAuth2 Pushed Authorization Request `request_uri` expiry configurable
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
The expires_in parameter in the PAR endpoint should be configurable via configuration properties or the DSL, allowing users to set the expiration duration based on their needs.
Current Behavior
Currently, the expires_in value is hardcoded, typically set to 30 seconds (soon to 5 minutes via https://github.com/spring-projects/spring-authorization-server/issues/2024), this is limiting flexibility and potentially causing issues with longer authorization flows.
Context
This limitation affects scenarios where longer authorization processes are needed, such as multi-factor authentication. Making this configurable would improve usability and compliance with various deployment requirements.
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 the OAuth2 Pushed Authorization Request (PAR) endpoint and the code that sets its hardcoded expires_in value. Trace how configuration properties and the DSL are exposed, then make the expiry configurable and verify that the PAR response reflects the configured duration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100