Difference between revisions of "Device flow usecase 1"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
| Line 1: | Line 1: | ||
= Device Flow = | = Device Flow = | ||
| − | + | OAuth 2.0 Device flow allows your IBM i application to deal with protected user data on remote resource, while users are not forced to share their usernames, passwords, and other private information. Instead, user jast have to pass authetification on remote resource and authorizate IBM i application to make some actions behalf of user. As far IBM i have no ability to display a web-page, it only provides user with link to authorization page. After user follow the link and accept request, i2rest-client will be granted for authorization token, which allows user data access. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 17:26, 3 April 2020
Device Flow
OAuth 2.0 Device flow allows your IBM i application to deal with protected user data on remote resource, while users are not forced to share their usernames, passwords, and other private information. Instead, user jast have to pass authetification on remote resource and authorizate IBM i application to make some actions behalf of user. As far IBM i have no ability to display a web-page, it only provides user with link to authorization page. After user follow the link and accept request, i2rest-client will be granted for authorization token, which allows user data access.
