Difference between revisions of "I2Rest Client"

From i2Rest
Jump to: navigation, search
Line 2: Line 2:
  
 
i2Rest-client is a native IBM i tool for web communications via http/https requests. It was intended to extend IBM i api functionality with http client functions. And more tnan this, with provided by I2rest-client Oauth 2.0 flows
 
i2Rest-client is a native IBM i tool for web communications via http/https requests. It was intended to extend IBM i api functionality with http client functions. And more tnan this, with provided by I2rest-client Oauth 2.0 flows
−
your IBM i api could have access to any OpenApi service.  
+
your IBM i API could have access to any OpenApi service.  
 +
 
 +
== Scenaries ==
 
Depending on your needs I2rest-client can provide four request authorization scenaries:
 
Depending on your needs I2rest-client can provide four request authorization scenaries:
−
 
−
::[[BasicAuth|Basic access authentication]]<BR>
 
−
::[[Client flow|Oauth2 CLient Credentials flow]]<BR>
 
−
::[[Device flow|Oauth2 Device flow]]<BR>
 
−
Http requests themself, JSON messages, stream file upload - everything under the first item. The same as above, but with [https://en.wikipedia.org/wiki/Basic_access_authentication  Basic access authentication] - under the second.
 
−
The last two cases are about the OAuth 2.0 authorization framework, which enables a third-party
 
−
application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction
 
−
between the resource owner and the HTTP service (Device flow), or by allowing the third-party application to obtain access on its own behalf (Client flow).
 
  
 
;Https request without authorization
 
;Https request without authorization
 
:<div id="noauth"></div>Http/https requests of any type, JSON messages, stream file upload - everything is here. Please explore [[NoAuth-usecase|typical usecases]]
 
:<div id="noauth"></div>Http/https requests of any type, JSON messages, stream file upload - everything is here. Please explore [[NoAuth-usecase|typical usecases]]
  
−
==Basic access authentication==
+
;Basic access authentication
 +
:<div id="BasicAuth"></div>Same options as above, but with [https://en.wikipedia.org/wiki/Basic_access_authentication]. Some [[BasicAuth-usercase|Usercases]] for a quik start.
 +
 
 +
;Oauth2 CLient Credentials flow
 +
:allowing the third-party application to obtain access on its own behalf
 +
 
 +
;Oauth2 Device flow
 +
:
  
−
<div id="BasicAuth"></div>Same features as above, but with [https://en.wikipedia.org/wiki/Basic_access_authentication]
 
  
  

Revision as of 12:26, 6 April 2020


i2Rest-client is a native IBM i tool for web communications via http/https requests. It was intended to extend IBM i api functionality with http client functions. And more tnan this, with provided by I2rest-client Oauth 2.0 flows your IBM i API could have access to any OpenApi service.

Scenaries

Depending on your needs I2rest-client can provide four request authorization scenaries:

Https request without authorization
Http/https requests of any type, JSON messages, stream file upload - everything is here. Please explore typical usecases
Basic access authentication
Same options as above, but with [1]. Some Usercases for a quik start.
Oauth2 CLient Credentials flow
allowing the third-party application to obtain access on its own behalf
Oauth2 Device flow


Implementation

You can interract with I2rest-client with IBM i command, or by the mean of it's integration API.

Retrieved from "https://www.i2rest.com/index.php?title=I2Rest_Client&oldid=137"