<commit_before>======
OpenId
======

A client uses the authorization grant to obtain an access token, which is a string representing an authorization granted to the client by the resource owner.
There're four grant-types (RFC-6749_):

Authorization code
------------------

* Applicable to a web application profile
* Main steps
** Resource owner grants access to the protected resource
** Authorization server returns an authorization code to the client (redirecting to the callback URI with authoriztion code in query)
** Client exchanges this authorization code for an acces token with the authorization server

Implicit workflow
-----------------

* Applicable to user-agent based application such as javascript (under the context of a webrowser)
* Main steps
** Resource owner grants access to the protected resource
** Access token is immediately returned to the client application in a hash fragment of the callback URL

Resource owner credentials workflow
-----------------------------------

* Application for nativate application
* Main steps
** The resource owner enters his credentials
** Client exhcanges the credentials with authorization server to get an access token

Client credentials workflow
---------------------------

* Main steps :
** Client application exchanges its own credentials for an access token. Protected resources is not owned by a specific user.

Hybrid workflow
---------------

TO COMPLETE

.. _RFC-6749: https://tools.ietf.org/html/rfc6749#section-1.3<commit_msg>Ticket 111 : Fix the bullet list :'(<commit_after>======
OpenId
======

A client uses the authorization grant to obtain an access token, which is a string representing an authorization granted to the client by the resource owner.
There're four grant-types (RFC-6749_):

Authorization code
------------------

* Applicable to a web application profile
* Main steps
    * Resource owner grants access to the protected resource
    * Authorization server returns an authorization code to the client (redirecting to the callback URI with authoriztion code in query)
    * Client exchanges this authorization code for an acces token with the authorization server

Implicit workflow
-----------------

* Applicable to user-agent based application such as javascript (under the context of a webrowser)
* Main steps
    * Resource owner grants access to the protected resource
    * Access token is immediately returned to the client application in a hash fragment of the callback URL

Resource owner credentials workflow
-----------------------------------

* Application for nativate application
* Main steps
    * The resource owner enters his credentials
    * Client exhcanges the credentials with authorization server to get an access token

Client credentials workflow
---------------------------

* Main steps :
    * Client application exchanges its own credentials for an access token. Protected resources is not owned by a specific user.

Hybrid workflow
---------------

TO COMPLETE

.. _RFC-6749: https://tools.ietf.org/html/rfc6749#section-1.3
{'fraction_non_alphanumeric': 0.11668305473615208, 'fraction_numerical': 0.010160603080957063, 'mean_word_length': 3.169398907103825, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7270829', 'n_tokens_mistral': 713, 'n_tokens_neox': 661, 'n_words': 371}