# django-rest-framework-jwt-refresh-token
Plugin for [django-rest-framework-jwt](https://github.com/GetBlimp/django-rest-framework-jwt) that supports [long running refresh tokens](https://auth0.com/docs/refresh-token).
[Documentation](https://lock8.github.io/django-rest-framework-jwt-refresh-token/)
Work initially done by [Nick Lang](https://github.com/fxdgear) from that [pull request](https://github.com/GetBlimp/django-rest-framework-jwt/pull/94).
[](https://travis-ci.org/lock8/django-rest-framework-jwt-refresh-token) [](https://codecov.io/github/lock8/django-rest-framework-jwt-refresh-token?branch=master)
## Usage
For a given long refresh token (stored in DB), POSTing to the delegate endpoint will return a new JWT token.
`bash http POST client_id=app grant_type="urn:ietf:params:oauth:grant-type:jwt-bearer" refresh_token=<REFRESH_TOKEN> api_type=app http://localhost:8000/delegate/ '{"token": "your_jwt_token_...", "refresh_token": "your long running refresh token..."}' `
## Changelog
- 0.5 / 2018-01-25
Make RefreshTokenViewSet a GenericViewSet to take advantage of schema generation
- 0.4 / 2018-01-18
Expose revoke functions as an API action
`POST /refresh_tokens/{key}/revoke/`
- 0.3 / 2018-01-16
Add refresh_token.revoke() to replace the current refresh token
- 0.2 / 2017-10-20
Add compatibility with Django 2.0
Drop Django support below 1.11
Drop DRF support below 3.6
- 0.1.2 / 2016-01-28
Fix packaging
- 0.1.1 / 2016-01-28
Fix packaging
- 0.1.0 / 2016-01-28
Initial Release based on https://github.com/GetBlimp/django-rest-framework-jwt/pull/123
Metadata
Release files for djangorestframework-jwt-refresh-token 0.5
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 | Actions |
|---|---|---|---|---|
| djangorestframework-jwt-refresh-token-0.5.tar.gz | 5.1 kB | Without provenance | Details for djangorestframework-jwt-refresh-token-0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| djangorestframework_jwt_refresh_token-0.5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for djangorestframework_jwt_refresh_token-0.5-py2.py3-none-any.whl |
Total release size: 28.1 kB
Release files / djangorestframework-jwt-refresh-token-0.5.tar.gz
| Download URL | djangorestframework-jwt-refresh-token-0.5.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
66e5794bf4bc26f5c973d3e76f903fc53b8a7629d1ff972d7586d6eb50606ff0
|
|
BLAKE2b-256 checksum How to use checksums |
568d0ed85797f67278580d42f828cfb9966560723b0802e1a546c00cf584acfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / djangorestframework_jwt_refresh_token-0.5-py2.py3-none-any.whl
| Download URL | djangorestframework_jwt_refresh_token-0.5-py2.py3-none-any.whl |
|---|---|
| Size | 23.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
d3f75c0d1c468e13775158841816af11de3c8e338fb22351b7a46388f73c7335
|
|
BLAKE2b-256 checksum How to use checksums |
032ff43ddfd2e4e44d1b7ed184170749cf445974d5d8ad300d095dc398d82da2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for djangorestframework-jwt-refresh-token 0.5
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.