Authentication agains Google Apps Domains for Django
googleappsauth allows you to authenticate your Django users against an Google Apps domain. This means you basically get a single sign-on solution, provided that all users of your django application also have Accounts in Google Apps for your Domain.
Usage
To use googleappsauth, configuration in settings.py should look like this:
GOOGLE_APPS_DOMAIN = 'example.com' GOOGLE_APPS_CONSUMER_KEY = 'example.com' GOOGLE_APPS_CONSUMER_SECRET = '*sekret*' # domain where your application is running GOOGLE_OPENID_REALM = 'http://*.hudora.biz/'
You also can tell googleappsauth where to go after successfull authentication, in case the redirect_url had not been set. LOGIN_REDIRECT_URL defaults to /.
LOGIN_REDIRECT_URL = '/admin'
To activate googleappsauth, set the appropriate Authentication backend and include a callback view.
settings.py:
AUTHENTICATION_BACKENDS = ('googleappsauth.backends.GoogleAuthBackend',)
urls.py:
(r'^callback_googleappsauth/', 'googleappsauth.views.callback'),
Using a special middleware which is included in the package, you can block access to a compete site.
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'googleappsauth.middleware.GoogleAuthMiddleware',
)
In addition you can set AUTH_PROTECTED_AREAS to authenticate only access to certain parts of a site, e.g.
AUTH_PROTECTED_AREAS = ['/admin']
Download
Get it at the Python Cheeseshop or at GitHub.
See also
Metadata
Release files for googleappsauth 1.03
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 | Actions |
|---|---|---|---|---|
| googleappsauth-1.03.tar.gz | 12.8 kB | Without provenance | Details for googleappsauth-1.03.tar.gz |
Release files / googleappsauth-1.03.tar.gz
| Download URL | googleappsauth-1.03.tar.gz |
|---|---|
| Size | 12.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b252f2c20f54e2e33e3c758c93a3759de963eca3e1788f017eb849514878a03
|
|
BLAKE2b-256 checksum How to use checksums |
8a5f7442185cd009e6b42ff6717aec54cc900c27348457c8b43f439468010e4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for googleappsauth 1.03
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.