Go to file
Andy Clayton 4e7116ca9e add natural key support to ResponseType
Have the option to use the more readable response type value rather than
the ResponseType id integer in fixtures and dumpdata output.

Prior to this change dumpdata represents response types like so:

    "response_types": [2]

And after this change when using `dumpdata --natural-foreign`:

    "response_types": [["code"]]
2018-08-20 10:49:00 -05:00
docs update docs for multiple response types per client 2018-08-17 09:54:30 -05:00
example Update example project. 2018-03-23 17:06:44 -03:00
oidc_provider add natural key support to ResponseType 2018-08-20 10:49:00 -05:00
.gitignore Simplify test suit. 2018-03-22 11:45:56 -03:00
.travis.yml Fix travis. 2018-07-12 15:28:14 -03:00
LICENSE Bump version v0.6.2. 2018-08-03 11:50:56 -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 Bump version v0.6.2. 2018-08-03 11:50:56 -03:00
tox.ini Pin pytest version. 2018-07-31 14:56: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.