Story #8192
Updated by bmbouter about 3 years ago
### Motivation
Pulp stores sensitive credentials, e.g. password for Basic Auth, proxy password, or client key for client certificate based authentication in the database in plaintext. The authentication and authorization mechanisms of Pulp keep these safe, but if the database itself was compromised, or dumped, those secrets would be readable to anyone with a copy.
### Proposal
Encrypt these credentials when they live in the database and decrypt them when they are used. This encryption would use symmetric encryption with a key stored on the filesystem that is generated at install time. A good option would be [Fernet symmetric key encryption from the `cryptography` library](https://cryptography.io/en/latest/fernet.html.).
### Related to [Story on Removing Secrets from API Response](https://pulp.plan.io/issues/8202)
The scope of the fields that are encrypted should be the same as those that are no longer returned in the API due to sensitivity. See [Story 8202](https://pulp.plan.io/issues/8202) for the list of fields.
### Installation Details
The private key will need to be generated at install time. We need to determine where to keep these by default securely. They need to be readable by code without a human involved.
.