Infra
/
lemur
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add additional wording around LEMUR_ENCRYPTION_KEYS

This commit is contained in:
Jasmine Schladen 2021-01-04 16:03:15 -08:00
parent 8a63b175e3
commit d2e9493397
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/administration.rst
View File

@ -151,6 +151,14 @@ Specifying the `SQLALCHEMY_MAX_OVERFLOW` to 0 will enforce limit to not create c
to start. Multiple keys can be provided to facilitate key rotation. The first key in the list is used for
encryption and all keys are tried for decryption until one works. Each key must be 32 URL safe base-64 encoded bytes.
Only fields of type `Vault` will be encrypted. At present, only the following fields are encrypted:
* `certificates.private_key`
* `pending_certificates.private_key`
* `dns_providers.credentials`
* `roles.password`
For implementation details, see `Vault` in `utils.py`.
Running lemur create_config will securely generate a key for your configuration file.
If you would like to generate your own, we recommend the following method: