No description
Find a file
Andy Clayton 9d5c2b39fa support introspection on client credentials tokens
The response can simply omit fields that require id_token as the only
required field is "active" according to RFC 7662. I think it would be
nice for introspection of client credentials tokens to be supported by
default without needing to override
OIDC_INTROSPECTION_VALIDATE_AUDIENCE_SCOPE, but this is a start.
2018-07-06 11:41:09 -05:00
docs support introspection on client credentials tokens 2018-07-06 11:41:09 -05:00
example Update example project. 2018-03-23 17:06:44 -03:00
oidc_provider support introspection on client credentials tokens 2018-07-06 11:41:09 -05:00
.gitignore Simplify test suit. 2018-03-22 11:45:56 -03:00
.travis.yml Remove Django 1.7 for travis. 2018-04-20 12:34:14 -03:00
LICENSE Bump version v0.4.3. 2016-11-02 12:28:39 -03:00
MANIFEST.in Fix translations handling 2016-11-24 13:09:19 +01:00
README.md Update README.md 2018-04-23 16:00:33 -03:00
setup.py Update setup.py 2018-04-27 14:47:07 -03:00
tox.ini Test docs with tox. 2018-04-20 18:23:41 -03:00

Django OpenID Connect Provider

Python Versions PyPI Versions Documentation Status Travis

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.

Read documentation for more info.

Do you want to contribute? Please read this.