Difference between revisions of "Authorization code usecase 1"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
Line 9: | Line 9: | ||
:d) Choose appropriate API method and scope on [https://developers.google.com/drive/api/v3/reference/files/list Google Drive Api page] | :d) Choose appropriate API method and scope on [https://developers.google.com/drive/api/v3/reference/files/list Google Drive Api page] | ||
− | ; | + | ;i2Rest comand composing |
− | :So what we need is: | + | :So what we need is:<br> |
+ | ::to set request method and API endpoint to values we prepared on Preparations step d; | ||
<pre> | <pre> | ||
I2REST COMMAND(*Get) | I2REST COMMAND(*Get) | ||
URL('https://www.googleapis.com/drive/v3/files') | URL('https://www.googleapis.com/drive/v3/files') | ||
− | </pre | + | </pre> |
− | :to | + | ::to specify properly configured on Preparations step B Certificate_Store to be able to work with SSL secured resource; |
− | |||
<pre> | <pre> | ||
DCMCLIENT(MYCLIENT) | DCMCLIENT(MYCLIENT) | ||
− | </pre | + | </pre> |
− | + | :: | |
AUTHMETHOD(*BRIDGE) | AUTHMETHOD(*BRIDGE) | ||
AUTHID('677815701888-aj80fure8f1laqd3dqvpqtmlandni5an | AUTHID('677815701888-aj80fure8f1laqd3dqvpqtmlandni5an | ||
Line 35: | Line 35: | ||
</pre> | </pre> | ||
− | ; | + | ;Oauth2 dialog |
:i2Rest Client will provide you with link - go ahead and follow it. | :i2Rest Client will provide you with link - go ahead and follow it. | ||
:[[File:Authorization_code_usecase1-1.png|600px]] | :[[File:Authorization_code_usecase1-1.png|600px]] | ||
Line 51: | Line 51: | ||
:[[File:Authorization_code_usecase1-4.png]] | :[[File:Authorization_code_usecase1-4.png]] | ||
<br> | <br> | ||
− | ; | + | ;Checking the result! |
:Here is server response: | :Here is server response: | ||
<pre> | <pre> |
Revision as of 13:26, 3 June 2020
Lets walk step by step through our example with getting the list of existing files on "i2restexample" user Google Drive.
- Preparations
- a) At the very beginning your application should be registered as a client (obtaining Device ID and Device Password) on Google (see details).
- b) Create *SYSTEM Certificate Store and add Google.com SSL CA .
- c) Register your i2Rest Client on your i2Rest Server as a client to enable "bridge mode".
- d) Choose appropriate API method and scope on Google Drive Api page
- i2Rest comand composing
- So what we need is:
- to set request method and API endpoint to values we prepared on Preparations step 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)
AUTHMETHOD(*BRIDGE) 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')
BRIDGEURL('https://api.i2rest.com:22089/a2d') BRIDGEID(OAUTH21) BRIDGEPW(oauth21)
- 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" } ] }