Difference between revisions of "I2Rest Client"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
Line 5: | Line 5: | ||
Depending on your needs I2rest-client can provide four request authorization scenaries: | Depending on your needs I2rest-client can provide four request authorization scenaries: | ||
− | :: | + | ::<BR> |
::[[BasicAuth|Basic access authentication]]<BR> | ::[[BasicAuth|Basic access authentication]]<BR> | ||
::[[Client flow|Oauth2 CLient Credentials flow]]<BR> | ::[[Client flow|Oauth2 CLient Credentials flow]]<BR> | ||
Line 14: | Line 14: | ||
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). | 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=== |
+ | |||
+ | Http/https requests of any type, JSON messages, stream file upload - everything is here. Please explore [[NoAuth-usecase|typical usecases]] | ||
+ | = Implementation = | ||
You can interract with I2rest-client [[i2Rest-client command|with IBM i command]], or by the mean of it's [[integration API]].<BR> | You can interract with I2rest-client [[i2Rest-client command|with IBM i command]], or by the mean of it's [[integration API]].<BR> |
Revision as of 11:14, 6 April 2020
i2Rest-client
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. Depending on your needs I2rest-client can provide four request authorization scenaries:
Http requests themself, JSON messages, stream file upload - everything under the first item. The same as above, but with 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
Http/https requests of any type, JSON messages, stream file upload - everything is here. Please explore typical usecases
Implementation
You can interract with I2rest-client with IBM i command, or by the mean of it's integration API.