Mentions légales du service

Skip to content
Snippets Groups Projects
Commit 234c55c1 authored by Pierre-Marie VAN HOUTEGHEM's avatar Pierre-Marie VAN HOUTEGHEM
Browse files

ch-iua simulator documentation fix

parent de5e26e1
No related branches found
No related tags found
No related merge requests found
...@@ -32,7 +32,7 @@ The ITI-71 transaction is sent by the Authorization Client to the Authorization ...@@ -32,7 +32,7 @@ The ITI-71 transaction is sent by the Authorization Client to the Authorization
Two ways can be used to resolve this transaction, but the one used by this simulator is the Authorization Code grant type. Two ways can be used to resolve this transaction, but the one used by this simulator is the Authorization Code grant type.
The request must be sent to the /authorize endpoint, which look like this The request must be sent to the /authorize endpoint, which look like this
``` http request ``` http
{$simulator.endpoint}/iua-simulator/rest/ch/authorize? {$simulator.endpoint}/iua-simulator/rest/ch/authorize?
``` ```
...@@ -51,7 +51,7 @@ The first Http Request is a GET containing the following parameters : ...@@ -51,7 +51,7 @@ The first Http Request is a GET containing the following parameters :
This request must be sent to the /authorize endpoint of the authorization server. This request must be sent to the /authorize endpoint of the authorization server.
This means the request should look like something like this : This means the request should look like something like this :
``` http request ``` http
HTTP GET {$simulator.endpoint}/iua-simulator/rest/ch/authorize? HTTP GET {$simulator.endpoint}/iua-simulator/rest/ch/authorize?
response_type=code response_type=code
&client_id=ch-iua-client &client_id=ch-iua-client
...@@ -81,7 +81,7 @@ Those arguments must therefore be contained in a body as an *application/x-www-f ...@@ -81,7 +81,7 @@ Those arguments must therefore be contained in a body as an *application/x-www-f
Finally both *client_id* and *client_secret* must be encapsulated in the base HTTP Authorization header. Finally both *client_id* and *client_secret* must be encapsulated in the base HTTP Authorization header.
This means the request should like something like this : This means the request should like something like this :
``` http request ``` http
HTTP POST {$simulator.endpoint}/iua-simulator/rest/ch/token HTTP 1.1 HTTP POST {$simulator.endpoint}/iua-simulator/rest/ch/token HTTP 1.1
Authorization: Basic vsdvZRTYHQS51SgvtsqeGFs62 Authorization: Basic vsdvZRTYHQS51SgvtsqeGFs62
Content-Type: application/x-www-form-urlencoded Content-Type: application/x-www-form-urlencoded
...@@ -113,7 +113,7 @@ The ITI-71 transaction is sent by the Authorization Client to the Authorization ...@@ -113,7 +113,7 @@ The ITI-71 transaction is sent by the Authorization Client to the Authorization
Two ways can be used to resolve this transaction, but the one used by this simulator is the Authorization Code grant type. Two ways can be used to resolve this transaction, but the one used by this simulator is the Authorization Code grant type.
The request must be sent to the /authorize endpoint, which look like this The request must be sent to the /authorize endpoint, which look like this
``` http request ``` http
{$simulator.endpoint}/iua-simulator/rest/ch/authorize? {$simulator.endpoint}/iua-simulator/rest/ch/authorize?
``` ```
...@@ -134,7 +134,7 @@ The first Http Request is a GET containing the following parameters : ...@@ -134,7 +134,7 @@ The first Http Request is a GET containing the following parameters :
This request must be sent to the /authorize endpoint of the authorization server. This request must be sent to the /authorize endpoint of the authorization server.
This means the request should look like something like this : This means the request should look like something like this :
``` http request ``` http
HTTP GET {$simulator.endpoint}/iua-simulator/rest/ch/authorize? HTTP GET {$simulator.endpoint}/iua-simulator/rest/ch/authorize?
response_type=code response_type=code
&client_id=ch-iua-client &client_id=ch-iua-client
...@@ -166,7 +166,7 @@ The scope request inside this request shall only contain permitted arguments : ...@@ -166,7 +166,7 @@ The scope request inside this request shall only contain permitted arguments :
Following this request, you will receive an Authorization Code in a JSON formatted response. Following this request, you will receive an Authorization Code in a JSON formatted response.
Using the Authorization client, you will then need to do a second Request to the following URL: Using the Authorization client, you will then need to do a second Request to the following URL:
``` http request ``` http
{$simulator.endpoint}/iua-simulator/rest/ch/token? {$simulator.endpoint}/iua-simulator/rest/ch/token?
``` ```
...@@ -184,7 +184,7 @@ Those arguments must therefore be contained in a body as an *application/x-www-f ...@@ -184,7 +184,7 @@ Those arguments must therefore be contained in a body as an *application/x-www-f
Finally both *client_id* and *client_secret* must be encapsulated in the base HTTP Authorization header. Finally both *client_id* and *client_secret* must be encapsulated in the base HTTP Authorization header.
This means the request should like something like this : This means the request should like something like this :
``` http request ``` http
HTTP POST {$simulator.endpoint}/iua-simulator/rest/ch/token HTTP 1.1 HTTP POST {$simulator.endpoint}/iua-simulator/rest/ch/token HTTP 1.1
Authorization: Basic vsdvZRTYHQS51SgvtsqeGFs62 Authorization: Basic vsdvZRTYHQS51SgvtsqeGFs62
Content-Type: application/x-www-form-urlencoded Content-Type: application/x-www-form-urlencoded
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment