DRF JWT Auth
Django REST Framework JWT Authentication package enables to authenticate to Django REST Framework's API Views and ViewSets by using JWT (in header or as query param).
In difference with other packages, this package offers the following features:
- The user autheticated is based on the payload info, so no user is loaded from database.
- So that, the user model that you will find on every
request.userwill be an instance ofdrfjwtauth.user.JWTUser, a class that keeps the same API thatdjango.contrib.auth.models.Userbut is not loaded from database and no write operations can be made over that user (due to it's not a model). - Provides a view (in
drfjwtauth.views.VerifyJWTView) to verify a token using a POST request. - NO login or token renew views are provided
Installation
$ pip install drf-jwt-auth
Setup
Authentication class
You can setup DRF JWT Auth as authentication class in two ways:
- As default authentication class adding to the
DEFAULT_AUTHENTICATION_CLASSESkey in the the global DRF settings:
REST_FRAMEWORK = {
[...]
'DEFAULT_AUTHENTICATION_CLASSES': ['...', 'drfjwtauth.auth.JWTAuth', '...'],
[...]
}
- In every APIView/ViewSet/view function:
from rest_framework.views import APIView
from drfjwtauth.auth import JWTAuth
class ExampleView(APIView):
authentication_classes = [JWTAuth]
@authentication_classes([JWTAuth])
def example_view(request, format=None):
[...]
Token Verify View
In your project's urls.py:
from django.urls import path
from drfjwtauth.views import VerifyJWTView
urlpatterns = [
[...],
path('token/verify/', VerifyJWTView.as_view(), name='token-verify')
[...],
]
Available settings and defaults
In your Django project's settings you can setup the following dict and keys:
DRF_JWT_AUTH = {
'ALGORITHM': JWT algorithm to sign tokens (HS256 by default).
'SIGNING_KEY': Secret key to sign tokens (same value as Django SECRET_KEY settings by default).
'AUTH_HEADER': Value before the token in the HTTP Authorization header (Bearer by default).
'QUERY_PARAM_NAME': Value before the query param name for HTTP GET requests (jwt by default).
}
Django management commands
This package adds two management commands that let's you to create JWT with a specific expiration date, generate_jwt and generate_jwt_from_db:
generate_jwt: Accept the next arguments to create a JWT without database based on default's Django User Model:username[positional][mandatory]-d,--expiration_date[mandatory]. A date in isoformat to invalidate the JWT.--id[optional]--first_name[optional]--last_name[optional]--email[optional]--is_active[optional]--is_staff[optional]--is_superuser[optional]--channels... [optional]--groups... [optional]--permissions... [optional]
For example:
python manage.py generate_jwt new_user -d 2030-12-31 --id 1 --first_name New --last_name User --email new_user@company.com --is_active --is_staff --channels a b --groups web_users --permissions can_visit_dashboards
generate_jwt_from_db: Given a username and a expiration date will return a JWT for the matched user in the database:username[positional][mandatory]-d,--expiration_date[mandatory]. A date in isoformat to invalidate the JWT.
For example:
python manage.py generate_jwt existing_user -d 2030-12-31
Metadata
Release files for drf-jwt-auth 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| drf-jwt-auth-0.2.3.tar.gz | 8.0 kB | Without provenance | Details |
Release files / drf-jwt-auth-0.2.3.tar.gz
| Download URL | drf-jwt-auth-0.2.3.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
837314c7620b5512a0fa1199fb3b9a3dd6146bcc5eb6b13c29e3a478f8d41128
|
|
BLAKE2b-256 checksum How to use checksums |
e20b7414cf64e440f1625094258e114bbfbac899642b3e4efc77dea77c338a12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.10
|
Security for drf-jwt-auth 0.2.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.