OpenID whitelist
django-openid-whitelist offers an easy way to keep your projects private.
After installation add your OpenID to the whitelist. With this OpenID it is possible to add another OpenID. If not disabled, each whitelisted OpenID can be used to whitelist more IDs.
For example - if there is OpenID A, with A it is possible to add OpenID B. Then with B it is possible to add another OpenID and so on.
It’s pretty intuitive to use this application.
Requirements
django >= 1.0
python-openid
Installation
install (for example easy_install django-openid-whitelist)
install python-openid
add ‘whitelist’ to your INSTALLED_APPS
run syncdb
include whitelist.urls (for example - url(r’^whitelist/’, include(‘whitelist.urls’))
form then accessible at whitelist/start
Simple form style whitelist_style.css included in whitelist/media installation directory.
Usage
To verify OpenID use whitelist-check and whitelist-check-json views. To add OpenID use whitelist-start. (names in quotes are named urls - simply use {% url whitelist-start %} in your template)
Also check view documentation in django admin.
Optional settings
- OPENID_TRUST_ROOT
Trust root for the OpenID Request. Defaults to the base URL of your page.
- OPENID_DISALLOW_INAMES
Disallow personal i-names. Defaults to false
Compatible with
- TracAuthOpenid
Add check_list and check_list_key to your [openid] section in trac.ini. check_list has to point to whitelist-check-json view. Set check_list_key to whatever you like (openid for example).
Metadata
Release files for django-openid-whitelist 0.3
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 |
|---|---|---|---|---|
| django-openid-whitelist-0.3.tar.gz | 9.2 kB | Without provenance | Details for django-openid-whitelist-0.3.tar.gz |
Release files / django-openid-whitelist-0.3.tar.gz
| Download URL | django-openid-whitelist-0.3.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bace4846d4326dc71d4a05865be209d5ed611f21290dc095ce333289bc1ff17f
|
|
BLAKE2b-256 checksum How to use checksums |
aee9919b23355d3bfbc74c5abca58ee5d438a14e5c756cb24da89f0baf38d8cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-openid-whitelist 0.3
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.