36018d19ae
The Dynamic Client Registration spec specifies multiple response_types and grant_types per client (https://openid.net/specs/openid-connect-registration-1_0.html#ClientMetadata). Since grant_types can be inferred from response_types we should be able to support both without needing to store grant_types. This also helps with oidc-client-js which expects a client that supports both "id_token" and "id_token token". |
||
|---|---|---|
| docs | ||
| example | ||
| oidc_provider | ||
| .gitignore | ||
| .travis.yml | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.md | ||
| setup.py | ||
| tox.ini | ||
Django OpenID Connect Provider
About OpenID
OpenID Connect is a simple identity layer on top of the OAuth 2.0 protocol, which allows computing clients to verify the identity of an end-user based on the authentication performed by an authorization server, as well as to obtain basic profile information about the end-user in an interoperable and REST-like manner. Like Google for example.
About the package
django-oidc-provider can help you providing out of the box all the endpoints, data and logic needed to add OpenID Connect (and OAuth2) capabilities to your Django projects.
Support for Python 3 and 2. Also latest versions of django.