# django-oidc-sub
[](https://travis-ci.org/tpazderka/django-oidc-sub) [](https://codecov.io/gh/tpazderka/django-oidc-sub)
> Django application for login through OpenID Connect
This library provides a database model for connection between AUTH_USER_MODEL and sub claim received from provider. It also provides an authentication backend that returns appropriate User based on the received sub claim.
## Table of Contents - [Dependencies](#dependencies) - [Configuration](#configuration) - [Testint](#testing) - [License](#license)
## Dependencies
Django >=1.11
mozilla-django-oidc
## Configuration
Add django_oidc_sub and mozilla_django_oidc to your installed apps.
Add django_oidc_sub.backends.OidcSubBackend to your AUTHENTICATION_BACKENDS.
## Testing
tox
## License
See [LICENSE](LICENSE)
Metadata
Release files for django-oidc-sub 0.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-oidc-sub-0.1.tar.gz | 3.1 kB | Without provenance | Details for django-oidc-sub-0.1.tar.gz |
Release files / django-oidc-sub-0.1.tar.gz
| Download URL | django-oidc-sub-0.1.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b14f8e043cc90ce00021b26ad9776045b722fa4b73b9a445609b55ecd2db0871
|
|
BLAKE2b-256 checksum How to use checksums |
2af5d8d7f69ca757843dccfc152ac0b56b12b2411b0aa628cdaef78c017d39f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-oidc-sub 0.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.