8000
Idea: introducing an approach to protect secrets in database · keycloak keycloak · Discussion #33045 · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the earlier Vault SPI design proposal, a second phase was proposed to introduce encryption and decryption capabilities. I have submitted a design proposal PR keycloak/keycloak-community#355 which builds upon that proposal and introduces a new SPI, called Encryption SPI, designed to protect secrets "at rest" during storage in the database. Please see a first draft of the proposal here.
I am interested in working on this topic to develop means for protecting sensitive data at rest without relying on solutions such as full-disk encryption. I’d appreciate hearing your thoughts and feedback on this topic.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the earlier Vault SPI design proposal, a second phase was proposed to introduce encryption and decryption capabilities. I have submitted a design proposal PR keycloak/keycloak-community#355 which builds upon that proposal and introduces a new SPI, called Encryption SPI, designed to protect secrets "at rest" during storage in the database. Please see a first draft of the proposal here.
I am interested in working on this topic to develop means for protecting sensitive data at rest without relying on solutions such as full-disk encryption. I’d appreciate hearing your thoughts and feedback on this topic.
Cc @pedroigor, @mhajas
Beta Was this translation helpful? Give feedback.
All reactions