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
Copy file name to clipboardExpand all lines: docs/source/installation.rst
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,11 +115,21 @@ Same as all other sensitive configurations, it's a good practice to load this fr
115
115
Changing this key after data has been created will prevent access to previously encrypted data. Chaning requires re-encrypting all existing data with the new key.
116
116
117
117
118
+
**JWT_SECRET_KEY**
119
+
120
+
A dedicated secret key used for signing and verifying JSON Web Tokens (JWTs). It should be a long, random string, independent of Django's ``SECRET_KEY`` and ``ENCRYPTION_SECRET_KEY``.
121
+
122
+
Using a separate key ensures that a JWT secret compromise does not affect other parts of your application.
123
+
124
+
Same as all other sensitive configurations, it's a good practice to load this from an environment variable or a secure vault.
0 commit comments