Authenticating Apache2 using your Django DB
Make sure you have apache2 mod-auth-external installed and configured (See: http://code.google.com/p/mod-auth-external/wiki/Configuration)
Define django-cliauth as your external authenticator by adding the following line in your virtualhost:
DefineExternalAuth django_cliauth pipe “/path/to/your/django-admin.py cliauth –settings=”YOUR_PROJECT.settings””
Set your authentication using a .htaccess file (or <Location> inside the virtualhost):
AuthType Basic
AuthName <authname>
AuthBasicProvider external
AuthExternal django_cliauth
Require valid-user
Reload your apache2 configuration
Checking is the user belongs to a group
Define django-cliauth as your external group checker by adding the following to your apache virtualhost:
DefineExternalGroup django_cliauth_grpck pipe “/path/to/your/django-admin.py cliauth –groupcheck –settings=’YOUR_PROJECT.settings’”
Set your authentication using a .htaccess file (or <Location> inside the virtualhost):
AuthType Basic
AuthName <authname>
AuthBasicProvider external
AuthExternal django_cliauth
GroupExternal django_cliauth_grpck
Require group <groupname1> <groupname2> …
Metadata
Release files for django-cliauth 0.9.1
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-cliauth-0.9.1.tar.gz | 2.1 kB | Without provenance | Details for django-cliauth-0.9.1.tar.gz |
Release files / django-cliauth-0.9.1.tar.gz
| Download URL | django-cliauth-0.9.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
baefe29454deb9bb1ef375f75705fe6216f3ae38a643b9a3d285a48fb5331e53
|
|
BLAKE2b-256 checksum How to use checksums |
1369ea8ac3abebc2a436428b88f6185e001b84c6eb8c52a19a25ddf668bee5fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-cliauth 0.9.1
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.