django-lux-sso-client
Lightweight Django OIDC client SDK for projects that authenticate against a
Dlux SSO provider. This package does not depend on django-lux.
This SDK is optional and Django-specific. Non-Django projects should connect to
the Dlux SSO provider with their platform's normal OIDC client library and
read the portable dlux_sso_role claim.
from dlux_sso_client.settings import configure_dlux_sso
configure_dlux_sso(
globals(),
issuer_url="https://sso.example.com",
client_id="client-id",
client_secret="client-secret",
role_mapping={
"staff_roles": ["admin", "staff"],
"groups": {"admin": ["Project Admins"], "staff": ["Project Staff"]},
},
)
Mount the OIDC client routes:
from django.urls import include, path
urlpatterns = [
path("accounts/sso/", include("dlux_sso_client.urls")),
]
Metadata
Release files for django-lux-sso-client 0.1.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 | |
|---|---|---|---|---|
| django_lux_sso_client-0.1.1.tar.gz | 6.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_lux_sso_client-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.8 kB
Release files / django_lux_sso_client-0.1.1.tar.gz
| Download URL | django_lux_sso_client-0.1.1.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fe6d7bb77b2614a4b73d3a5a67b78f6a24a0fc78529f42d14662e151cd156ca
|
|
BLAKE2b-256 checksum How to use checksums |
5d186bf4441f32862f3de571cc759faa1eda475cc9cae5a01bcd6dd729504a3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 12, 2026.
Transparency logRelease files / django_lux_sso_client-0.1.1-py3-none-any.whl
| Download URL | django_lux_sso_client-0.1.1-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa773622c47a25c399fc827c0b67f532e421d596924f6540d6d5607f5a424e50
|
|
BLAKE2b-256 checksum How to use checksums |
c065cf0a0b18b8fc53eaae862f1cf172be755f8ec5fcb3eef4c3dd4e0fa86172
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 12, 2026.
Transparency logSecurity for django-lux-sso-client 0.1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for django_lux_sso_client-0.1.1.tar.gz
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 Jun 12, 2026.
Transparency logA 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.