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
On user registration, PBKDF2/Argon2 (the latter seems to be better nowadays) will be used to create an encryption key (MK) for the user.
A RSA public/private key pair will also be generated
Public key is stored in DB as-is. Private key is stored encrypted with the MK from step one.
When a user wants to add new AWS/Azure secrets, it can easily be encrypted with the public key in the database.
When deploy endpoint is called (ie. when the secrets need to be decrypted), the private key will be decrypted and the private key will be used to decrypt the secrets.
How step 5 will get the MK: How will the frontend/CLI store the master key once a user logs in?.
On login, the API will generate the MK and send it back in a response to be stored in an http-only secure cookie.
Cookie from step 1 will be attached with every request. It will only be stored in-memory for API endpoints that need them.
Note
This issue was auto-created by a Trello x GitHub integration
Original Link:
Allow for user signup and secure storage of user secrets in DB
Card Contents:
The text was updated successfully, but these errors were encountered: