spring-projects / spring-projects/spring-boot
EndpointRequest should provide matcher regardless of endpoint exposure
Open
Nobody has claimed this yet.
type: enhancement
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
Currently, EndpointRequest provides matchers only for the exposed endpoints. This causes endpoint security to behave differently based on whether the endpoint returns a 200 (when it’s exposure is true) or a 404 (when it’s not included in the exposed endpoints). Someone might want to secure the endpoint regardless of whether it returns a 200 or 404
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 the EndpointRequest entry point and trace how endpoint exposure affects the matchers it provides. Confirm that security can match an endpoint consistently for both a 200 response when exposed and a 404 response when it is not exposed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100