Skip to content

Database-backed settings for mozilla-django-oidc, with modified unique identifiers for users

License

Notifications You must be signed in to change notification settings

maykinmedia/mozilla-django-oidc-db

Folders and files

NameName
Last commit message
Last commit date

Latest commit

b2338ba Β· Jan 27, 2025
Nov 22, 2024
Feb 7, 2024
Jan 27, 2025
Jan 23, 2025
Nov 25, 2024
Dec 10, 2024
Jul 2, 2021
Jun 26, 2024
Nov 22, 2024
Jan 23, 2025
Jan 27, 2025
Jul 2, 2021
Feb 7, 2024
Jan 27, 2025
Feb 5, 2024
Jan 27, 2025
Jan 23, 2025

Repository files navigation

Version:0.22.0
Source:https://github.com/maykinmedia/mozilla-django-oidc-db
Keywords:OIDC, django, database, authentication

build-status Coverage status black

python-versions django-versions pypi-version

Database-backed settings for mozilla-django-oidc, with modified unique identifiers

  • Thin layer on top of mozilla-django-oidc
  • Allows configuration of OpenID Connect variables via django-solo
  • Overrides mozilla-django-oidc default behaviour, using the sub claim instead of the email claim as unique identifier for users

mozilla-django-oidc-db provides a database singleton for several configuration variables required for mozilla-django-oidc, moving them from deploy-time to run-time. This enables modification of the configuration, without having to restart the application.

Additionally, mozilla-django-oidc-db by default uses the sub (subject) claim instead of the email claim as the unique identifier for users in the RP (Relying Party) application. Using email as the unique identifier is not recommended, as mentioned in the OpenID Connect specification.

Please see the hosted documentation for installation, configuration and usage instructions.

About

Database-backed settings for mozilla-django-oidc, with modified unique identifiers for users

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published