Difference between revisions of "Device flow description"

From i2Rest
Jump to: navigation, search
(→‎Device flow by i2Rest command)
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{DISPLAYTITLE:Device flow description}}
 
{{DISPLAYTITLE:Device flow description}}
 
==Overview==
 
==Overview==
−
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. <br>
 
[[File:Device-flow-scheme1.png|400px]]
 
[[File:Device-flow-scheme1.png|400px]]
 
<br>
 
<br>
Line 8: Line 8:
 
(A) i2Rest Client initiates the flow with a request to the authorization server. The request incudes client identifier and requested scope.<br>  
 
(A) i2Rest Client initiates the flow with a request to the authorization server. The request incudes client identifier and requested scope.<br>  
 
(B) The authorization server responds with a device code, an end-user code and the verification URL.<br>  
 
(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 URI and thus instructs the end user to visit authorization page using a user agent on another device.<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)At the time end-user  i2 rest starts polling authorization server.<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 validates the device code provided by the client and responds with the access token if the client is granted access, an error if they are denied access, or an indication that the client should continue to poll.<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>
  
 
==Device flow by i2Rest command==
 
==Device flow by i2Rest command==
 
The next parameters are mandatory to perform request with Device flow by I2Rest command.<br>
 
The next parameters are mandatory to perform request with Device flow by I2Rest command.<br>
 +
 
{| class="wikitable"
 
{| class="wikitable"
−
! Parameter!! Description
+
! Keyword !! Parameter!! Description
 
|-
 
|-
−
|[[I2Rest_Client_command#AUTHMETHOD | Authentication method]] || *OAUTH2D must be specified
+
|[[I2Rest_Client_command#AUTHMETHOD | AUTHMETHOD]] || Authentication method ||*OAUTH2D must be specified
 
|-
 
|-
−
|[[I2Rest_Client_command#COMAND| Command]] || Any of available request type can be choosen
+
|[[I2Rest_Client_command#COMAND| COMAND ]] || Request type || Any of available request type can be choosen
 
|-
 
|-
−
|[[I2Rest_Client_command#URL| API endpoint]] || HTTP resource to serve the request
+
|[[I2Rest_Client_command#URL| URL ]] || API endpoint || HTTP resource to serve the request
 
|-
 
|-
−
|[[I2Rest_Client_command#AUTHID| User/OAuth2 client/device ID]] ||rowspan="2"|  Credentials to authenticate i2Rest Client with authorization server
+
|[[I2Rest_Client_command#AUTHID| AUTHID]] || User/OAuth2 client/device ID ||rowspan="2"|  Credentials to authenticate I2Rest Client with authorization server
 
|-
 
|-
−
|[[I2Rest_Client_command#AUTHPW| User/OAuth2 client/dev passwd]]
+
|[[I2Rest_Client_command#AUTHPW| AUTHPW]] || User/OAuth2 client/dev passwd
 
|-
 
|-
−
|[[I2Rest_Client_command#AUTHURL| OAuth2 authorization endpoint]] || HTTP resource to be requested for an authorization URL and device 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| OAuth2 token endpoint]] || HTTP resource to be requested for an access token
+
|[[I2Rest_Client_command#TOKENURL| TOKENURL]] ||Token endpoint ||HTTP resource to be requested for an access token
 
|-
 
|-
−
|[[I2Rest_Client_command#SCOPE| Scope]] || The set of resources and operations that are allowed to application with access token  
+
|[[I2Rest_Client_command#SCOPE| SCOPE]] || Scope || The set of resources and operations that are allowed to application with access token  
 
|-
 
|-
 
|}
 
|}
Line 44: Line 45:
 
       AUTHMETHOD(*OAUTH2D)                                       
 
       AUTHMETHOD(*OAUTH2D)                                       
 
       DCMCLIENT(MYCLIENT)                                   
 
       DCMCLIENT(MYCLIENT)                                   
−
      RECVLOG('/home/btpl/recv.log')                     
+
       TOKENS('/tokens/tokens.usrspc')
−
      SENTLOG('/home/btpl/sent.log')                     
+
       AUTHID('<client ID>')                 
−
       TOKENS('/qsys.lib/qtemp.lib/tokens.usrspc')
+
       AUTHPW('<client secret>')                   
−
       AUTHID('677815701888-dfa6i6tcrvqpvmc1acii98ij32h7lc3j
 
−
              .apps.googleusercontent.com')                 
 
−
       AUTHPW('2Rstk_A-u4rbLcm6OFcclMz5')                   
 
 
       AUTHURL('https://oauth2.googleapis.com/device/code')  
 
       AUTHURL('https://oauth2.googleapis.com/device/code')  
 
       TOKENURL('https://oauth2.googleapis.com/token')       
 
       TOKENURL('https://oauth2.googleapis.com/token')       
 
       SCOPE('https://www.googleapis.com/auth/drive.file')
 
       SCOPE('https://www.googleapis.com/auth/drive.file')
 
</pre>
 
</pre>
−
 
−
----
 
−
[[I2Rest_Client|Back to i2Rest Client]]
 

Latest revision as of 13:04, 9 September 2020

Overview

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.
Device-flow-scheme1.png
Device flow scheme.

(A) i2Rest Client initiates the flow with a request to the authorization server. The request incudes client identifier and requested scope.
(B) The authorization server responds with a device code, an end-user code and the verification URL.
(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.
(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.
(E) i2Rest Client starts polling authorization server with device code to determine whether the user has authorized the request.
(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.

Device flow by i2Rest command

The next parameters are mandatory to perform request with Device flow by I2Rest command.

Keyword Parameter Description
AUTHMETHOD Authentication method *OAUTH2D must be specified
COMAND Request type Any of available request type can be choosen
URL API endpoint HTTP resource to serve the request
AUTHID User/OAuth2 client/device ID Credentials to authenticate I2Rest Client with authorization server
AUTHPW User/OAuth2 client/dev passwd
AUTHURL OAuth2 authorization endpoint HTTP resource to be requested for an authorization URL and device code
TOKENURL Token endpoint HTTP resource to be requested for an access token
SCOPE Scope The set of resources and operations that are allowed to application with access token

i2Rest command example bellow represents request for creating i2rest.doc file on Google Drive, please explore the appropriate use case. 

I2REST COMMAND(*POST)                                       
       URL('https://www.googleapis.com/drive/v3/files')     
       BODY(*N '{"name":"i2rest.doc"}' 
            'application/json' *YES 1208)
       OUTPUT(*BOTH)  
       AUTHMETHOD(*OAUTH2D)                                      
       DCMCLIENT(MYCLIENT)                                  
       TOKENS('/tokens/tokens.usrspc')
       AUTHID('<client ID>')                 
       AUTHPW('<client secret>')                   
       AUTHURL('https://oauth2.googleapis.com/device/code') 
       TOKENURL('https://oauth2.googleapis.com/token')      
       SCOPE('https://www.googleapis.com/auth/drive.file')
Retrieved from "https://www.i2rest.com/index.php?title=Device_flow_description&oldid=1862"