spring-projects / spring-projects/spring-security
On Abstain Access Should be Denied
Open
Nobody has claimed this yet.
in: core
type: enhancement
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
We should look in every location and require that if an authorization manager abstained, then access should be denied. One option is that if the AuthorizationResult is null, then deny access. Another option is to require AuthorizationResult to be non-null going forward.
This depends on:
- #11958
- #11967
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 reviewing every authorization location that handles AuthorizationResult, along with the completed dependencies #11958 and #11967. Done means abstentions consistently deny access, with one clearly defined non-null or denial behavior applied everywhere.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authorization, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100