kumi/django-oidc-provider
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Improve docs.

Browse source
This commit is contained in:
Ignacio Fiorentino 2016-09-08 17:32:57 -03:00
parent 439774aeeb
commit 2c5019af3e
2 changed files with 3 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/index.rst
View file

@ -1,7 +1,7 @@
Welcome to Django OIDC Provider Documentation! Welcome to Django OIDC Provider Documentation!
============================================== ==============================================
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. And as a side effect a fair implementation of OAuth2.0 too. This tiny (but powerful!) package can help you providing out of the box all the endpoints, data and logic needed to add OpenID Connect capabilities to your Django projects. And as a side effect a fair implementation of OAuth2.0 too. Covers Authorization Code, Implicit and Hybrid flows.
Also implements the following specifications: Also implements the following specifications:
@ -13,7 +13,6 @@ Also implements the following specifications:
Before getting started there are some important things that you should know: Before getting started there are some important things that you should know:
* Despite that implementation MUST support TLS. You can make request without using SSL. There is no control on that. * Despite that implementation MUST support TLS. You can make request without using SSL. There is no control on that.
* This library covers **Authorization Code Flow** and **Implicit Flow**, NO support for **Hybrid Flow** at this moment.
* Supports only for requesting Claims using Scope values. * Supports only for requesting Claims using Scope values.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------

2
docs/sections/relyingparties.rst
View file

@ -18,7 +18,7 @@ Properties
* ``client_type``: Values are ``confidential`` and ``public``. * ``client_type``: Values are ``confidential`` and ``public``.
* ``client_id``: Client unique identifier. * ``client_id``: Client unique identifier.
* ``client_secret``: Client secret for confidential applications. * ``client_secret``: Client secret for confidential applications.
* ``response_type``: Values are ``code``, ``id_token`` and ``id_token token``. * ``response_type``: Values depends of wich flow you want use.
* ``jwt_alg``: Clients can choose wich algorithm will be used to sign id_tokens. Values are ``HS256`` and ``RS256``. * ``jwt_alg``: Clients can choose wich algorithm will be used to sign id_tokens. Values are ``HS256`` and ``RS256``.
* ``date_created``: Date automatically added when created. * ``date_created``: Date automatically added when created.