Difference between revisions of "I2Rest Client"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
| Line 18: | Line 18: | ||
;Oauth2 Device flow | ;Oauth2 Device flow | ||
:Provided by i2Rest-client OAuth 2.0 Device flow allows your IBM i application to deal with protected user data on remote resource, while end users are not forced to share their usernames, passwords, and other private information. Detailed flow decription can be found [[Device-flow-decription|here]], typical usecases - [[Device-flow-usecase|here]] | :Provided by i2Rest-client OAuth 2.0 Device flow allows your IBM i application to deal with protected user data on remote resource, while end users are not forced to share their usernames, passwords, and other private information. Detailed flow decription can be found [[Device-flow-decription|here]], typical usecases - [[Device-flow-usecase|here]] | ||
| − | |||
Revision as of 12:58, 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 than 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
- Oauth2 CLient Credentials flow
- allowing the third-party application to obtain access on its own behalf
- Oauth2 Device flow
- Provided by i2Rest-client OAuth 2.0 Device flow allows your IBM i application to deal with protected user data on remote resource, while end users are not forced to share their usernames, passwords, and other private information. Detailed flow decription can be found here, typical usecases - here
Implementation
You can interract with I2rest-client with IBM i command, or by the mean of it's integration API.
