No description
bdb2fdb8f5
This commit fixes the JS callback defined in the check-session iframe which can produce infinite callback loops if the received message doesn't come from the relying party. In that case another message is posted to the source of the message (which can be the OP itself) thus resulting in an infinite loop because "error" messages are continuously generated by the callback function. |
||
---|---|---|
docs | ||
example | ||
oidc_provider | ||
.gitignore | ||
.travis.yml | ||
CHANGELOG.md | ||
LICENSE | ||
MANIFEST.in | ||
README.md | ||
setup.py | ||
tox.ini |
Django OIDC 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 capabilities to your Django projects.
Support for Python 3 and 2. Also latest versions of django.
Contributing
Join us! we love contributions, so please feel free to fix bugs, improve things, provide documentation. You SHOULD follow this steps:
- Fork the project.
- Make your feature addition or bug fix.
- Add tests for it inside
oidc_provider/tests
. Then run all and ensure everything is OK (read docs for how to test in all envs). - Send pull request to the
develop
branch.