django-rest-knox
Authentication module for Django rest auth.
Knox provides easy-to-use authentication for Django REST Framework The aim is to allow for common patterns in applications that are REST-based, with little extra effort; and to ensure that connections remain secure.
Knox authentication is token-based, similar to the TokenAuthentication
built into DRF. However, it overcomes some problems present in the
default implementation:
-
DRF tokens are limited to one per user. This does not facilitate securely signing in from multiple devices, as the token is shared. It also requires all devices to be logged out if a server-side logout is required (i.e. the token is deleted).
Knox provides one token per call to the login view - allowing each client to have its own token which is deleted on the server side when the client logs out.
Knox also provides an option for a logged-in client to remove all tokens that the server has - forcing all clients to re-authenticate.
-
DRF tokens are stored unencrypted in the database. This would allow an attacker unrestricted access to an account with a token if the database were compromised.
Knox tokens are only stored in a secure hash form (like a password). Even if the database were somehow stolen, an attacker would not be able to log in with the stolen credentials.
-
DRF tokens track their creation time, but have no inbuilt mechanism for tokens expiring. Knox tokens can have an expiry configured in the app settings (default is 10 hours.)
More information can be found in the Documentation
Run the tests locally
If you need to debug a test locally and if you have docker installed,
simply run the ./docker-run-tests.sh script and it will run the test suite in every Python /
Django versions.
You could also simply run regular tox in the root folder as well, but that would make testing the matrix of
Python / Django versions a bit more tricky.
Work on the documentation
Our documentation is generated by Mkdocs.
You can refer to their documentation on how to install it locally.
Another option is to use mkdocs.sh in this repository.
It will run mkdocs in a docker container.
Running the script without any params triggers the serve command.
The server is exposed on localhost on port 8000.
To configure the port the serve command will be exposing the server to, you
can use the following env var:
MKDOCS_DEV_PORT="8080"
You can also pass any mkdocs command like this:
./mkdocs build
./mkdocs --help
Check the Mkdocs documentation for more.
1 maintainer
Metadata
1 maintainer
Release files for django-rest-knox 5.1.0
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 | |
|---|---|---|---|---|
| django_rest_knox-5.1.0.tar.gz | 21.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_rest_knox-5.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 37.0 kB
Release files / django_rest_knox-5.1.0.tar.gz
| Download URL | django_rest_knox-5.1.0.tar.gz |
|---|---|
| Size | 21.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78307dce32858679fe96afb06c4ab2d4fe0ed085c7a739a7ccc03a14dea2b37b
|
|
BLAKE2b-256 checksum How to use checksums |
458d14c8e67495f0e01fd26929c34d2fbebd910c20f9f3dcc268fadb93a009ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Release files / django_rest_knox-5.1.0-py3-none-any.whl
| Download URL | django_rest_knox-5.1.0-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7dad21e91091db07796ea96f559fd2e1f67b8d42748d4e140d2fa7a0319538e7
|
|
BLAKE2b-256 checksum How to use checksums |
1d20188535a919c642a20fef171571e5b3470c3323c4be952602e709a0790edf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Security for django-rest-knox 5.1.0
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.
