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 an effort to increase security we should default to reading JDBC configuration values from the Vault. Only if values are not found in the vault should we fall back to the usual config mechanism.
This should be implemented specifically for the following properties:
edc.datasource.<name>.user
edc.datasource.<name>.password
edc.datasource.<name>.url
Every one of these should be read from the Vault first, and config later.
Which Areas Would Be Affected?
SQL pool implementation
Why Is the Feature Desired?
security
Solution Proposal
Attempt to read the property from the vault first, and if not found fall back to config, but issue a warning
The text was updated successfully, but these errors were encountered:
paullatzelsperger
changed the title
Read sensitive informatino from Vault: database credentials
Read sensitive information from Vault: database credentials
Apr 22, 2024
Feature Request
In an effort to increase security we should default to reading JDBC configuration values from the
Vault
. Only if values are not found in the vault should we fall back to the usual config mechanism.This should be implemented specifically for the following properties:
edc.datasource.<name>.user
edc.datasource.<name>.password
edc.datasource.<name>.url
Every one of these should be read from the
Vault
first, and config later.Which Areas Would Be Affected?
SQL pool implementation
Why Is the Feature Desired?
security
Solution Proposal
Attempt to read the property from the vault first, and if not found fall back to config, but issue a warning
The text was updated successfully, but these errors were encountered: