spring-projects / spring-projects/spring-security
Add support for RFC7807-style error responses
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
There should be an option to enable RFC7807-style ProblemDetail-responses when using Spring Security 6.
Current Behavior
There is currently no option to enable this.
Context
For the last three years, our company have used RFC7807 problem responses in our Spring Applications, first through zalando problem and after Spring 6 / Spring Boot 3 we have moved to the built in ProblemDetails-objects provided with Spring MVC.
We are currently using a custom built security filter for authenticating user tokens, but we wish to move to Spring Security. However we cannot find any way of enabling ProblemDetails in error-responses (For example when returning a 401) without completely writing this ourselves. Should this maybe be implemented as an option in a coming release?
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 locating Spring Security's authentication error-response handling and compare it with Spring MVC's built-in ProblemDetail support; done means an option can produce RFC7807-style responses for authentication errors such as 401 without requiring a custom security filter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100