Encryption
Description
Configuration for the application's encryption.
Danger
If an encryption key is not provided then sensitive information will be stored in plain text in certain columns of the database (namely those related to connecting to 3rd party services).
This is probably fine for dev installations but should be avoided in production.
Generate an encryption key with this command:
| Bash | |
|---|---|
Save the key this generates and either
- Set it as an environment variable. e.g.
TIGRQC_ENCRYPTION_KEY=your-generated-key - Store it in a file and provide the path to it. e.g.
TIGRQC_ENCRYPTION_KEY=/path/to/your/keyfile
If this key is lost or changed any currently encrypted information in the database will become permanently unreadable. It should also be protected and kept secret.
Therefore
- Back the key up securely.
- Never commit your key to any git repository.
- If you save the key in a file, restrict permissions so only the user that runs the tigrqc app can read it.
Encryption Settings
Optional Settings
TIGRQC_ENCRYPTION_KEY- Description: A fernet key or the path to a file containing a fernet key. If unset, certain sensitive columns in the database will be stored in plain text.
- Default:
None