spring-projects / spring-projects/spring-security
SEC-2316: Unable to specify ConfigAttribute RUN_AS_ in a straight-forward way
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Stefan Norberg (Migrated from SEC-2316) said:
Hi,
I need to specify the RUN_AS_ROLE_FOO config attribute on a method/bean, but as there is no support for @RunAs (and that the JEE spec doesn't seem to allow that to method level anyway?) I am forced to add the RUN_AS_ROLE_FOO.
My issue is that I can't add the RunAs-functionality without adding an ACL that hence will deny all access to the method/bean.
It would be nice to have RUN_AS_ROLE to have it's own annotation for clarity.
It's not very user friendly at this point and the documentation is not very clear on how to use the run-as-functionality.
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 existing RUN_AS_ROLE_FOO configuration and the documentation covering run-as functionality. Clarify how a dedicated annotation should apply to a method or bean and interact with ACLs. Done means the run-as role can be specified clearly without requiring an unrelated ACL that denies access, with the usage documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100