spring-projects / spring-projects/spring-security
SEC-3123: Encrypted property value support
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
sreekanth (Migrated from SEC-3123) said:
Its good to have encrypted property value support for property file, now we have to use jasypt to enable this functionality unfortunately jasypt doesn't have support for @PropertySource (java config). Though jasypt support or not its good to have it as a part of spring or spring security framework itself, since it adds value to the end user by not fiddling with third party libraries. So primary request is to do a inbuilt support for encrypted property value in spring/spring security framework.
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
No source files, tests, or entry points are identified. Start by reviewing how Spring or Spring Security handles property files and @PropertySource, comparing the requested built-in behavior with Jasypt; done would be agreed, implemented support for encrypted property values without relying on a third-party library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100