Difference between revisions of "Authorization code usecase 1"

From i2Rest
Jump to: navigation, search
(i2Rest Client command composing)
Line 10: Line 10:
 
== i2Rest Client command composing ==   
 
== i2Rest Client command composing ==   
 
So what we need composing i2Rest Client command is:<br>
 
So what we need composing i2Rest Client command is:<br>
:to set request method and API endpoint to values we prepared on Preparations step (d);   
+
:to set request method and API endpoint to values that are specified in the API method description (d);   
 
<pre>
 
<pre>
 
I2REST COMMAND(*Get)                                       
 
I2REST COMMAND(*Get)                                       
Line 19: Line 19:
 
       DCMCLIENT(MYCLIENT)   
 
       DCMCLIENT(MYCLIENT)   
 
</pre>  
 
</pre>  
:to specify obtained on Preparations step (a) and step (d) requisites;
+
:to specify obtained on Preparations step (a) requisites;
 
<pre>
 
<pre>
 
       AUTHID('677815701888-aj80fure8f1laqd3dqvpqtmlandni5an
 
       AUTHID('677815701888-aj80fure8f1laqd3dqvpqtmlandni5an
Line 29: Line 29:
 
       SCOPE('https://www.googleapis.com/auth/drive.file')   
 
       SCOPE('https://www.googleapis.com/auth/drive.file')   
 
</pre>   
 
</pre>   
:to specify Bridge mode parameters obtained on Preparations step (c).
+
:to specify Bridge mode parameters obtained on Preparations step (c). Make sure that the <code>BRIDGEURL</code> matches Redirection URI specified during the client registration on Preparation step (a).
 
<pre>
 
<pre>
 
       AUTHMETHOD(*BRIDGE)   
 
       AUTHMETHOD(*BRIDGE)   

Revision as of 14:56, 4 June 2020

The usecase shows how to use I2Rest Client request with Oauth2 Authorization code flow. We will call Google Drive Api in order to get the list of existing files on "i2restexample" user Google Drive.

Preparations

The next steps are to be performed before we can compose and execute i2Rest Client command.

a) Your application should be registered as a client (obtaining Device ID and Device Password) on Google (see details).
b) Insure that you have Google SSL CA installed. Install it if needed.
c) Register your i2Rest Client on your i2Rest Server as a client to enable "bridge mode" by setting up your i2Rest Server OAuth2 object.


i2Rest Client command composing

So what we need composing i2Rest Client command is:

to set request method and API endpoint to values that are specified in the API method description (d);
I2REST COMMAND(*Get)                                       
       URL('https://www.googleapis.com/drive/v3/files') 
to specify properly configured on Preparations step (b) Certificate_Store to be able to work with SSL secured resource;
       DCMCLIENT(MYCLIENT)  
to specify obtained on Preparations step (a) requisites;
       AUTHID('677815701888-aj80fure8f1laqd3dqvpqtmlandni5an
              .apps.googleusercontent.com')                   
       AUTHPW(tI2ezmVGioGwrGk9K2O23Mv5)                       
       AUTHURL('https://accounts.google.com/o/oauth2/v2/auth  
               ')                                             
       TOKENURL('https://oauth2.googleapis.com/token')        
       SCOPE('https://www.googleapis.com/auth/drive.file')  
to specify Bridge mode parameters obtained on Preparations step (c). Make sure that the BRIDGEURL matches Redirection URI specified during the client registration on Preparation step (a).
       AUTHMETHOD(*BRIDGE)  
       BRIDGEURL('https://api.i2rest.com:22089/a2d')          
       BRIDGEID(OAUTH21)                                      
       BRIDGEPW(oauth21) 

All the necessary parameters are specified, it's time to execute the complete command.

I2REST COMMAND(*GET)                                            
       URL('https://www.googleapis.com/drive/v3/files')         
       OUTPUT(*BOTH)                                            
       DCMCLIENT(MYCLIENT)                                      
       RECVLOG('/home/btpl/recv.log')                           
       SENTLOG('/home/btpl/sent.log')                           
       AUTHMETHOD(*BRIDGE)                                      
       TOKENS('/qsys.lib/qtemp.lib/tokens.usrspc')              
       AUTHID('1052056765075-qv2u4rgmhs6rgoijpribg64ffvtgdhi    
              6.apps.googleusercontent.com')                    
       AUTHPW(HDXLMOqhdtnSZ5CfCZBWQOsQ)                         
       AUTHURL('https://accounts.google.com/o/oauth2/v2/auth    
               ')                                               
       TOKENURL('https://oauth2.googleapis.com/token')          
       SCOPE('https://www.googleapis.com/auth/drive.file')      
       BRIDGEURL('https://api.i2rest.com:22089/a2d')            
       BRIDGEID(OAUTH21)
       BRIDGEPW(oauth21)

Authorization code flow dialog

i2Rest Client will provide end user with link to follow.
style="padding: 10px"

After entering the Bridge user code end user will be redirect to authorization server.
Authorization code usecase1-5.png

End user suggested to perform user authentication.
Authorization code usecase1-2.png

End user suggested to grant access to requested scope.
Authorization code usecase1-3.png

Now end user is redirected back to i2Rest bridge.
Authorization code usecase1-4.png

Checking the result!

Here is server response:

Server response (status 200, shown 214 bytes of 214):   
    {                                                       
     "kind": "drive#fileList",                              
     "incompleteSearch": false,                             
     "files": [                                             
      {                                                     
       "kind": "drive#file",                                
       "id": "1b-aQhiVeXgAQZVYeftIpuBo2GCvKQzHz",           
       "name": "i2rest.doc",                                
       "mimeType": "application/msword"                     
      }                                                     
     ]                                                      
    }                                                       


Back to i2Rest Client