-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEC-3123: Encrypted property value support #3323
Comments
Rob Winch said: Moving to Spring Security for consideration |
Sam Brannen said: Please note that this is related to the following issues.
|
👍 |
@rwinch thanks for taking it up, is this improvement in streamline ? |
@sreekanthsnair Thanks for the comment. @pivotal-joe-grandja is taking this on |
Thanks @rwinch and @pivotal-joe-grandja 👍 |
@jgrandja any updates on this ? |
@sreekanthsnair Unfortunately there hasn't been any movement on this as of yet. I've been working on other higher priority items. Will update you as soon as work starts on this. |
@sreekanthsnair FYI...There are initial efforts on extracting a spring-vault project from spring-cloud-vault that is likely going to support encrypting properties w/ vault cc @jgrandja |
Is there a way i can use encryption for my datasource without using spring cloud @sreekanthsnair |
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.
The text was updated successfully, but these errors were encountered: