spring-projects / spring-projects/spring-security
Support Externalized Method Security Configuration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
There are times that users cannot add annotations to objects or APIs that they want to secure. For example, consider if an team external provides a PersonService and team internal wants to add security to it. At the moment, the security must be done by adding intercept-methods style configuration.
A similar situation occurs when using Collections of objects. In this case, Spring Security provides custom Filtering. This could potentially be used to replace the @PreFilter and @PostFilter support.
I think that these situations are very similar and can be combined into an approach similar to Jackson's MixIn Approach.
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 with the linked intercept-methods documentation and compare the proposal with Jackson's MixIn approach. The issue also mentions collection filtering as a possible replacement for @PreFilter and @PostFilter. No files or tests are named, and completion would require an agreed design for externalized method security configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100