Difference between revisions of "I2Rest Client"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | 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. | + | = 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: | Depending on your needs I2rest-client can provide four request authorization scenaries: | ||
::[[NoAuth|Http/Https request without authorization]]<BR> | ::[[NoAuth|Http/Https request without authorization]]<BR> | ||
| Line 7: | Line 8: | ||
::[[Client flow|Oauth2 CLient Credentials flow]]<BR> | ::[[Client flow|Oauth2 CLient Credentials flow]]<BR> | ||
::[[Device flow|Oauth2 Device flow]]<BR> | ::[[Device flow|Oauth2 Device flow]]<BR> | ||
| + | |||
| + | The last two cases are with 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). | ||
| + | |||
| + | You can interract with I2rest-client [[i2Rest-client command|with the green screen terminal interface]], or by the mean of it's integration api, or even call it within your application via The Execute Command (QCMDEXC) API.<BR> | ||
Revision as of 14:13, 2 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:
The last two cases are with 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).
You can interract with I2rest-client with the green screen terminal interface, or by the mean of it's integration api, or even call it within your application via The Execute Command (QCMDEXC) API.
