django-pyoidc
This library allows Single Sign On (SSO) integration into Django through the Open ID Connect (OIDC) protocol.
It can be used to set up a Single Sign On using an identity provider (Keycloak, etc.) or to login using Google, Twitter, etc.
Warning: this library has not been audited. However, we are based on pyoidc which we believe is a sane OIDC implementation.
We tried to make OpenID Connect (OIDC) configuration as easy and secure as possible. However everything can be customized, and we tried to take into account every use case in the library design. If you are not satisfied with the default configuration, take a look at the cookbook or the setting reference.
Features
- Easy configuration through premade
Providerclasses (see the list here) - Authenticate users from multiple providers
- Bearer authentication support for django-rest-framework integration (single provider)
- drf-spectacular : your swagger page will allow to connect to your OIDC provider
- Easy integration with the Django permission system
- Highly customizable design that should suit most needs
- Support back-channel logout
- Support service accounts (accounts for machine-to-machine authentication)
- Sane and secure defaults settings
Roadmap
- Frontchannel logout
- Switch to django signal system login/logout hooks
- Allow for audience check without customizing
get_userusing a setting
Acknowledgement
This library is built on the work of many others. First of all, thanks to all the maintainers of pyoidc as they did all the spec implementation. This library is mostly about glue between Django and pyoidc.
We were also heavily inspired by:
mozilla-django-oidcfor its login redirection URI managementdjango-auth-oidcfor its hook system
If you want to understand why we decided to implement our own library, this is documented here.
Documentation
The documentation is graciously hosted at readthedocs.
Installation
First, install the python package:
pip install django_pyoidc
Then add the library app to your django applications, after django.contrib.sessions and django.contrib.auth:
INSTALLED_APPS = [
"django.contrib.auth",
"django.contrib.sessions",
...
"django_pyoidc"
]
Remember to add the session middleware! Add in your settings.py:
MIDDLEWARE = [
"django.contrib.sessions.middleware.SessionMiddleware",
]
Now is the time to run a migrate operation, as we create a database table (read why here). Run in your project dir:
./manage.py migrate
We also need a cache (read why here), so let's configure a dumb one for development purposes. Add in your settings.py:
CACHES = {
"default": {
"BACKEND": "django.core.cache.backends.locmem.LocMemCache",
"LOCATION": "unique-snowflake",
}
}
Now you can pick an identity provider from the available providers. Provider classes are a quick way to generate the library configuration and URLs. You can also configure the settings manually, but this is not recommended if you are not familiar with the OpendID Connect (OIDC) protocol.
Add the following DJANGO_PYOIDC to your settings.py:
# settings
DJANGO_PYOIDC = {
# This is the name that your identity provider will have within the library
"sso": {
# change the following line to use your provider
"provider_class": "django_pyoidc.providers.keycloak_18.Keycloak18Provider",
# your secret should not be stored in settings.py, load them from an env variable
"client_secret": os.getenv("SSO_CLIENT_SECRET"),
"client_id": os.getenv("SSO_CLIENT_ID"),
"provider_discovery_uri": "https://keycloak.example.com/auth/realms/fixme",
# This setting allow the library to cache the provider configuration auto-detected using
# the `provider_discovery_uri` setting
"oidc_cache_provider_metadata": True,
}
Finally, add OIDC views to your url configuration (urls.py):
from django_pyoidc.helper import OIDCHelper
# `op_name` must be the name of your identity provider as used in the `DJANGO_PYOIDC` setting
oidc_helper = OIDCHelper(op_name="sso")
urlpatterns = [
path(
"auth/",
include((oidc_helper.get_urlpatterns(), "django_pyoidc"), namespace="auth"),
),
]
And you are ready to go!
If you struggle with those instructions, take a look at the quickstart tutorial.
Usage/Examples
We wrote an extensive collection of 'how-to' guides in the documentation.
Appendix
Commercial support
This project is sponsored by Makina Corpus. If you require assistance on your project(s), please contact us: contact@makina-corpus.com
Report a security vulnerability
License
Authors
Metadata
Release files for django-pyoidc 1.0.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_pyoidc-1.0.13.tar.gz | 1.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_pyoidc-1.0.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / django_pyoidc-1.0.13.tar.gz
| Download URL | django_pyoidc-1.0.13.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f36de1829998fe6a197640b6cd41a8d83be90551c93b11bd8fdba4a5ba43c38a
|
|
BLAKE2b-256 checksum How to use checksums |
ac629e5428af3a888296f95a435513c616a5dc52718f6c79410e20e6315ac7c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 16, 2026.
Transparency logRelease files / django_pyoidc-1.0.13-py3-none-any.whl
| Download URL | django_pyoidc-1.0.13-py3-none-any.whl |
|---|---|
| Size | 35.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db477db9503deb25fb999d4be22376a09d01bc6849cfe6261ec3d1fd2b55a037
|
|
BLAKE2b-256 checksum How to use checksums |
b4e9636eaa8e7807d94531e62e598ed7ac92e89cf746505948377236e6bc0a69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 16, 2026.
Transparency log