Skip to content
This repository was archived by the owner on May 26, 2020. It is now read-only.

Commit 6daefea

Browse files
committed
Merge pull request #168 from kumar303/security
Adds some notes to the docs about security
2 parents 4abffd4 + 0306a94 commit 6daefea

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

docs/index.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,16 @@ If you want to know more about JWT, check out the following resources:
3131
- Django (1.6, 1.7)
3232
- Django REST Framework (2.4, 3.0, 3.1, 3.2)
3333

34+
## Security
35+
36+
Unlike some more typical uses of JWTs, this module only generates
37+
authentication tokens that will verify the user who is requesting one of your DRF
38+
protected API resources. The actual
39+
request parameters themselves are *not* included in the JWT claims which means
40+
they are not signed and may be tampered with. You should only expose your API
41+
endpoints over SSL/TLS to protect against content tampering and certain kinds of
42+
replay attacks.
43+
3444
## Installation
3545

3646
Install using `pip`...
@@ -175,7 +185,8 @@ Default is `True`.
175185

176186
### JWT_VERIFY_EXPIRATION
177187

178-
You can turn off expiration time verification with by setting `JWT_VERIFY_EXPIRATION` to `False`.
188+
You can turn off expiration time verification by setting `JWT_VERIFY_EXPIRATION` to `False`.
189+
Without expiration verification, JWTs will last forever meaning a leaked token could be used by an attacker indefinitely.
179190

180191
Default is `True`.
181192

0 commit comments

Comments
 (0)