Difference between revisions of "I2Rest Client"
Pavel.lobko (talk | contribs) |
(→Scenaries) |
||
Line 13: | Line 13: | ||
:Same options as above, but with [[Basic_access_authentication | Basic access authentication]]. Some [[I2Rest_Client_Usecases#Basic_access_authentication|Usecases]] for a quik start. | :Same options as above, but with [[Basic_access_authentication | Basic access authentication]]. Some [[I2Rest_Client_Usecases#Basic_access_authentication|Usecases]] 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. [[Client_flow_description|More]] about I2Rest Client Flow. Some usecases - [[I2Rest_Client_Usecases#Oauth2_Client_Credentials_flow|here]]. | :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 - [[I2Rest_Client_Usecases#Oauth2_Client_Credentials_flow|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 [[Device_flow_description|here]], typical usecases - [[I2Rest_Client_Usecases#Oauth2_Device_flow|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. General flow description can be found [[Device_flow_description|here]], typical usecases - [[I2Rest_Client_Usecases#Oauth2_Device_flow|here]]. | ||
+ | |||
+ | ;OAuth2 Access code flow using i2Rest bridge mode | ||
+ | TODO | ||
== Implementation == | == Implementation == | ||
<div id="implementation"></div>You can interract with I2rest-client [[i2Rest_Client_command|with IBM i command]], or by the mean of it's [[integration API]].<BR> | <div id="implementation"></div>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 16:13, 21 May 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 Usecases 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.
- OAuth2 Access code flow using i2Rest bridge mode
TODO
Implementation
You can interract with I2rest-client with IBM i command, or by the mean of it's integration API.