NOTE! django-admin-sso uses Google’s oauth2client which has been deprecated for a long time; the repository has even been archived by Google now. django-admin-sso isn’t going anywhere but I’d recommend that new projects use django-authlib’s Admin OAuth support.
Django admin SSO
Django admin SSO lets users login to Django’s administration panel using an OAuth2 provider instead of a username/password combination.
Installation
django-admin-sso is most often used with Google OAuth2 and the instructions follow that assumption. At least in theory it is possible to use a different OAuth2 provider.
Make sure you have a working Django project setup.
Install django-admin-sso using pip:
pip install django-admin-sso
Add admin_sso to INSTALLED_APPS in your settings.py file:
INSTALLED_APPS = ( ... 'admin_sso', ... )Add the django-admin authentication backend:
AUTHENTICATION_BACKENDS = ( 'admin_sso.auth.DjangoSSOAuthBackend', 'django.contrib.auth.backends.ModelBackend', )Insert your OAuth2 client id and secret key into your settings file:
DJANGO_ADMIN_SSO_OAUTH_CLIENT_ID = 'your client id here' DJANGO_ADMIN_SSO_OAUTH_CLIENT_SECRET = 'your client secret here'
Navigate to Google’s Developer Console, create a new project, and create a new client ID under the menu point “APIs & AUTH”, “Credentials”. The redirect URI should be of the form http://example.com/admin/admin_sso/assignment/end/
Run ./manage.py migrate to create the needed database tables.
Log into the admin and add an Assignment.
Assignments
Any Remote User -> Local User X
Select Username mode “any”.
Set Domain to your authenticating domain.
Select your local user from the User drop down.
Remote User -> Local User
Select Username mode “matches” or “don’t match”.
Set username to [not] match by.
Set Domain to your authenticating domain.
Select your local user from the User drop down.
Changelog
3.0
Dropped support for Django<1.11 and Python<3.
Modernized the package and reformatted the code using black.
2.4
Official support for Django 1.11.
2.3
Raised the minimum supported Django version to the LTS version, 1.8.
Avoid deprecation warnings with Django 1.10.
2.2
Official support for Django 1.10 (no changes were necessary)
Made the admin panel usable on sites with many users.
2.1
Removed support for OpenID
Python 3 compatible
Dropped support for Django versions older than 1.7
Continued development as django-admin-sso (2.0.x versions were released independently as django-admin-sso2)
1.0
Add support for OAuth2.0 since google closes its OpenID endpoint https://developers.google.com/accounts/docs/OpenID
Using OpenID is now deprecated and OpenID support will be removed in a future release.
Add more tests to get a decent coverage.
Metadata
Release files for django-admin-sso 5.2.0
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-admin-sso-5.2.0.tar.gz | 9.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_admin_sso-5.2.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 18.5 kB
Release files / django-admin-sso-5.2.0.tar.gz
| Download URL | django-admin-sso-5.2.0.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
878f1776825c8454c440781153b9a7a755192f97f6a09d66961cd2d1066fd04c
|
|
BLAKE2b-256 checksum How to use checksums |
9ee318b343f1521a2b82ea6dff612f1c9435fe88f6a677d29b3b9147f964e9b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / django_admin_sso-5.2.0-py2.py3-none-any.whl
| Download URL | django_admin_sso-5.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
5cab4c9a3746a60c36f384ec7aa9cd4bc6eb73f44de6bcdba7293346d31fcfc8
|
|
BLAKE2b-256 checksum How to use checksums |
729f43610a18d199447a02a7a90a73546c844200b256715633f1305214d7cf22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for django-admin-sso 5.2.0
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.