Difference between revisions of "I2Rest Client"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
| Line 14: | Line 14: | ||
;Oauth2 CLient Credentials flow | ;Oauth2 CLient Credentials flow | ||
| − | : | + | :Should be used to authentificate your IBM i application on remote resource to work with its own data rather than a user's data. [[Client-flow-description|More]] about I2Rest Client Flow. Some usecases - [[Client-flow-usecase|here]]. |
;Oauth2 Device flow | ;Oauth2 Device flow | ||
Revision as of 10:04, 8 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
- Basic access authentication
- Same options as above, but with Basic access authentication. Some Usercases for a quik start.
- Oauth2 CLient Credentials flow
- Should be used to authentificate your IBM i application on remote resource to work with its own data rather than a user's data. More about I2Rest Client Flow. Some usecases - here.
- 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. General flow description 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.
