Difference between revisions of "Client flow description"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
| Line 23: | Line 23: | ||
|[[i2Rest-client command#TOKENS| Tokens storage]] || Any of available request type can be choosen | |[[i2Rest-client command#TOKENS| Tokens storage]] || Any of available request type can be choosen | ||
|- | |- | ||
| − | |[[i2Rest-client command#AUTHID| User/OAuth2 client/device ID]] || | + | |[[i2Rest-client command#AUTHID| User/OAuth2 client/device ID]] ||rowspan="2"| Client Credentials to authenticate with authorization server |
|- | |- | ||
| − | |[[i2Rest-client command#AUTHPW| User/OAuth2 client/dev passwd]] | + | |[[i2Rest-client command#AUTHPW| User/OAuth2 client/dev passwd]] |
|- | |- | ||
| − | |[[i2Rest-client command#TOKENURL| OAuth2 token endpoint]] || | + | |[[i2Rest-client command#TOKENURL| OAuth2 token endpoint]] || HTTP resource to be requested by the client for an access token. |
|- | |- | ||
|} | |} | ||
Revision as of 12:37, 10 April 2020
An application can request an access token using only its own credentials, the flow is pretty simple.
The flow consists of the following steps:
(A) The client authenticates with the authorization server and requests an access token from the token endpoint.
(B) The authorization server authenticates the client, and if valid, issues an access token.
So, the next parameters are required
| Parameter | Description |
|---|---|
| Authentication method | *OAUTH2C has to be chosen |
| Command | Any of available request type can be choosen |
| API endpoint | Any of available request type can be choosen |
| Tokens storage | Any of available request type can be choosen |
| User/OAuth2 client/device ID | Client Credentials to authenticate with authorization server |
| User/OAuth2 client/dev passwd | |
| OAuth2 token endpoint | HTTP resource to be requested by the client for an access token. |
Back to i2Rest Client
i2Rest client perfoms Oauth 2.0 Client credential flow when *OAUTH2C Authentication method is chosen.
