Skip to main content

Django Federated Login

Django Federated Login provides an authentication bridge between Django projects and OpenID-enabled identity providers. The bridge is pre-wired to be used with a single Google Apps domain, but could be extended to be linked with other OpenID providers also. It is different from other OpenID consumers as this consumer only allows connecting to a pre-defined identity provider.

The provided backend matches users based on the e-mail address returned from the identity provider. If no matching user could be found, a user account can optionally be created.

Installation

Installation with pip:

$ pip install django-federated-login

Add 'federated_login' to your list of installed apps:

settings.py:
INSTALLED_APPS = (
    ...
    'federated_login',
)

Add 'federated_login.auth.backend.EmailBackend' as authentication backend:

settings.py:
AUTHENTICATION_BACKENDS = (
    'federated_login.auth.backends.EmailBackend',
    'django.contrib.auth.backends.ModelBackend',
)

Provide the Google Apps domain to identify against:

settings.py:
FL_APPS_DOMAIN = 'webatoom.nl'

Register the views:

urls.py:
url(r'^federated/', include('federated_login.urls')),

Usage

Point your browser to /federated/login/. You might want to include a button to this url on the regular login page.

Extra settings

These are the customizable settings:

FL_APPS_DOMAIN

Google Apps domain to identify against.

FL_CREATE_USERS (Default: False)

Whether to create a user account when unknown e-mail address is presented.

FL_USER_FACTORY (Default: 'aba.utils.fl_user_factory')

Function that is called when creating a user account.

FL_SSO_ENDPOINT (Default: Google Apps)

Override this setting to link with another OpenID identity provider.

Notes

This package depends on a fork of python-openid as the current upstream version (2.2.5) does not play well with a Google extension used by Google Apps identity provider.

Metadata

Release files for django-federated-login 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-federated-login 0.1.2
File Size Uploaded Provenance Actions
django-federated-login-0.1.2.tar.gz 5.3 kB Without provenance Details for django-federated-login-0.1.2.tar.gz

Release files / django-federated-login-0.1.2.tar.gz

Download URL django-federated-login-0.1.2.tar.gz
Size 5.3 kB
Tags Source
SHA-256 checksum
How to use checksums
a1682e143f4b14e5c31a7ca37032b9d775061d33efd2c72d22486116e2d67e8a
BLAKE2b-256 checksum
How to use checksums
a2dadaf1886f7038a06d6d59cea8e133c5f2ff809e5a06bd9867dd315a60431b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for django-federated-login 0.1.2

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page