spring-projects / spring-projects/spring-security
SEC-2364: Keep authorities fresh
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
ZhangLiangliang (Migrated from SEC-2364) said:
A commons requirment is : Admin A update user B's authorities while user B has logged in,
and require user B could apply his new new authorities immediately without relogin.
My first thought is implementing custom UserDetailsService and UserDetails.
Make every call UserDetails#getAuthorities() is call DAO.
But whitout custom AuthenticationProvider this is could not reached.
Because AuthenticationProviders SEC provideed ( DaoAuthenticationProvider、CasAuthenticationProvider etc)
will copy authorities form UserDetails, apply AuthoritiesMapper and store them in Authentication object,
this will make authorities is cached.
Should/Could this be improved?
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 the AuthenticationProvider implementations and UserDetails#getAuthorities() behavior described in the issue, including how authorities are copied into Authentication. The issue does not name files or tests; a concrete design and acceptance criteria for applying updated authorities without relogin would need to be established first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100