spring-projects / spring-projects/spring-security
SEC-2452: obtainSecurityMetadataSource from database
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
zhangyuan (Migrated from SEC-2452) said:
Thank you for your great work , guys.
In our system, different users have different roles, different roles have different authorities, that is common, ritht?
The problem is before our system is start up, our programers have no idea which role have which kind of authorities, for example, they donn't konw '/produdt/insert.action' belongs to 'insert' role, so they cann't write this authorities code in our system. this should be done be a administrator in a web page, add a RequestMatcher and ConfigAttribute or some kind of that stuff in the web page, when the user login in the page, query the obtainSecurityMetadataSource from database each time or form the cache, that is what I'm looking for.
But in version like 3.2.0 or below, it is hard to extend some spring security classes to do the right thing, I have to write a lot of code by myself. I'm wondering is there any chances you guys can make a nicer interfate for me to extend?
Thank you.
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 issue's discussion of obtainSecurityMetadataSource, RequestMatcher, ConfigAttribute, and loading metadata from a database or cache. No repository files, tests, or concrete acceptance criteria are named, so maintainer clarification is needed before defining the extension point and what completion should verify.
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
- 20/100