Django Always Authenticated
A middleware that ensures that a request always has an authenticated user.
If the request doesn’t have an authenticated user, it logs in a default user. If the default user doesn’t exist, it is created.
Compatibility
This middleware has been tested with these versions of Django:
1.7
1.8
1.9
1.10
master (at the time of the release)
Setup
Install from PyPI:
pip install django_always_authenticated
Add to MIDDLEWARE (MIDDLEWARE_CLASSES for Django <1.10) in settings file:
MIDDLEWARE = (
...
'always_authenticated.middleware.AlwaysAuthenticatedMiddleware',
)
As a security safeguard, the middleware will raise an ImproperlyConfiguredException when running in production mode (DEBUG=False). To run the middleware in production, set ALWAYS_AUTHENTICATED_DEBUG_ONLY to False.
Configuration
This middleware reads these settings:
ALWAYS_AUTHENTICATED_USERNAME
A string with the name of the default user, defaults to 'user'.
ALWAYS_AUTHENTICATED_USER_DEFAULTS
A dict with additional default values to set when creating the user.
ALWAYS_AUTHENTICATED_DEBUG_ONLY
Set to False to allow running with DEBUG=False.
Example project
There is a very single example project that demonstrates the middleware in the directory example_project.
Running Tests
To run the tests, install the requirements and run py.test:
pip install -r requirements.txt py.test
You can also use tox to run the tests with all supported versions of Python and Django:
pip install tox tox
Metadata
Release files for django-always-authenticated 0.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 | Actions |
|---|---|---|---|---|
| django-always-authenticated-0.1.0.tar.gz | 2.9 kB | Without provenance | Details for django-always-authenticated-0.1.0.tar.gz |
Release files / django-always-authenticated-0.1.0.tar.gz
| Download URL | django-always-authenticated-0.1.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f111220d27cc1951f965afc63ffa42e716e1ca7f84ab5aa010bd73c0fde4e76
|
|
BLAKE2b-256 checksum How to use checksums |
9c69b083b81ab31692412388fbd3a799156891b6f7d27e95c192caba7ada5a31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-always-authenticated 0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.