Difference between revisions of "Client flow description"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
| Line 9: | Line 9: | ||
:'''(B)''' The authorization server authenticates the client, and if valid, issues an access token. | :'''(B)''' The authorization server authenticates the client, and if valid, issues an access token. | ||
| − | + | == Required parameters == | |
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 12:54, 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.
Required parameters
| Parameter | Description |
|---|---|
| Authentication method | *OAUTH2C must be specified
|
| Command | Any of available request type can be choosen |
| API endpoint | HTTP resource to serve the request |
| Tokens storage | ??????? |
| User/OAuth2 client/device ID | Client Credentials to authenticate with authorization server |
| User/OAuth2 client/dev passwd | |
| OAuth2 token endpoint | HTTP resource used by the client to abtain an access token |
Back to i2Rest Client
i2Rest client perfoms Oauth 2.0 Client credential flow when *OAUTH2C Authentication method is chosen.
