Device flow description - Revision history

Pavel.lobko at 10:04, 9 September 2020

2020-09-09T10:04:12Z

2020-07-09T08:58:32Z

2020-07-09T08:57:41Z

‎Overview

2020-07-09T06:54:33Z

2020-05-29T10:26:21Z

‎Device flow by i2Rest command

2020-05-29T10:25:37Z

‎Device flow by i2Rest command

2020-05-29T10:24:10Z

‎Device flow by i2Rest command

2020-05-29T10:06:34Z

2020-05-29T10:03:15Z

‎Overview

2020-05-29T10:00:01Z

‎Device flow by i2Rest command

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:Device flow description}}
 ==Overview==
-[https://tools.ietf.org/html/rfc8628 Oauth 2.0 Device flow] is the authorization scenario for those devices (like IBM i), that has no ability to display an authorization web page when making request to private data on resources with limited access.
+[https://tools.ietf.org/html/rfc8628 Oauth 2.0 Device flow] is the authorization scenario for those devices (like IBM i), that has no ability to display an authorization web page when making request to private data on resources with limited access. <br>
 [[File:Device-flow-scheme1.png|400px]]
 <br>

← Older revision		Revision as of 08:58, 9 July 2020
Line 52:		Line 52:
	SCOPE('https://www.googleapis.com/auth/drive.file')		SCOPE('https://www.googleapis.com/auth/drive.file')
	</pre>		</pre>
−
−	~~----~~
−	~~[[I2Rest_Client\|Back to i2Rest Client]]~~

@@ Line 9: / Line 9: @@
 (B) The authorization server responds with a device code, an end-user code and the verification URL.<br>
 (C) i2Rest Client displays an end-user code and the verification URL and thus instructs the end user to visit authorization page using a user agent on another device.<br>
-(D) The end-user follows provided verification URL on any browser capable device.<br>
+(D) The end-user follows provided verification URL on any browser capable device. The authorization server authenticates the resource owner and performs authorization dialog to determin either access will be granted or denied.<br>
 (E) i2Rest Client starts polling authorization server with device code to determine whether the user has authorized the request.<br>
 (F) The authorization server authenticates the client, performs validation of the device code, and, if access was granted by end user, responds with an access token.<br>

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:Device flow description}}
 ==Overview==
-[https://tools.ietf.org/html/rfc8628 Oauth 2.0 Device flow] is the authorization scenario for those devices (like IBM i), that has no ability to display an authorization web page when making request to private data on resources with limited access. When application runing on a such device trying to access some protected data,<br>
+[https://tools.ietf.org/html/rfc8628 Oauth 2.0 Device flow] is the authorization scenario for those devices (like IBM i), that has no ability to display an authorization web page when making request to private data on resources with limited access.
 [[File:Device-flow-scheme1.png|400px]]
 <br>

@@ Line 15: / Line 15: @@
 ==Device flow by i2Rest command==
 The next parameters are mandatory to perform request with Device flow by I2Rest command.<br>
-{| class="wikitable"
 {| class="wikitable"
 ! Keyword !! Parameter!! Description
 |-
-|[[I2Rest_Client_command#AUTHMETHOD | AUTHMETHOD]] || Authentication method || *BRIDGE must be specified
+|[[I2Rest_Client_command#AUTHMETHOD | AUTHMETHOD]] || Authentication method ||*OAUTH2D must be specified
 |-
 |[[I2Rest_Client_command#COMAND| COMAND ]] || Request type || Any of available request type can be choosen

@@ Line 48: / Line 48: @@
 |[[I2Rest_Client_command#AUTHPW| AUTHPW]] || User/OAuth2 client/dev passwd
 |-
-|[[I2Rest_Client_command#AUTHURL| AUTHURL ]] ||OAuth2 authorization endpoint || HTTP resource to be requested for an authorization code
+|[[I2Rest_Client_command#AUTHURL| AUTHURL ]] ||OAuth2 authorization endpoint ||  HTTP resource to be requested for an authorization URL and device code
 |-
 |[[I2Rest_Client_command#TOKENURL| TOKENURL]] ||Token endpoint ||HTTP resource to be requested for an access token
 |-
 |[[I2Rest_Client_command#SCOPE| SCOPE]] || Scope || The set of resources and operations that are allowed to application with access token
 |-
 |}

@@ Line 33: / Line 33: @@
 |-
 |[[I2Rest_Client_command#SCOPE| Scope]] || The set of resources and operations that are allowed to application with access token
 |-
 |}

@@ Line 44: / Line 44: @@
         AUTHMETHOD(*OAUTH2D)
         DCMCLIENT(MYCLIENT)
         TOKENS('/tokens/tokens.usrspc')
         AUTHID('<client ID>')