I ran into a problem and can't figure out how to solve it.
ISAM version 9.0.7.2
preToken and postToken scripts almost from template
If I send an "empty" request to device_authorize - everything works (almost perfect, I'm missing id_token in /token, but I can put it there based on the suggestion from
https://community.ibm.com/community/user/security/ communities/community-home/digestviewer/viewthread?MessageKey=5098215c-c0a4-4c6d-8cac-79158e825fb9&CommunityKey=e7c36119-46d7-42f2-97a9-b44f0cc89c6d#bm5098215c-c0a4-4c6d-8cac-25)
POST
https://idpdev.delta.sbrf.ru/mga/sps/oauth/oauth20/device_authorize?client_id=devicetestAnd I get a response:
{
"user_code": "uo1t-ulcs",
"device_code": "SjIV51ypc304lZnKt4ZUM80tgv5rm0",
"scope": "",
"interval": 5,
"verification_uri_complete": "https://idp/mga/sps/oauth/oauth20/user_authorize?user_code=uo1t-ulcs",
"verification_uri": "https://idp/mga/sps/oauth/oauth20/user_authorize",
"expires_in": 299
}
After entering the login, password and permission confirmation (nothing), I can go to /token or /user_info and get acess_token (or id_token, collected according to the workaround from the article above)
But the standard information about the user is not enough for me, I need to add a scope to call, but then the device flow "turns into a pumpkin"...
POST
https://idpdev.delta.sbrf.ru/mga/sps/oauth/oauth20/device_authorize?client_id=devicetest2&scope=openidI will also get an answer:
{
"user_code": "uo1t-ulcs",
"device_code": "SjIV51ypc304lZnKt4ZUM80tgv5rm0",
"scope": "openid",
"interval": 5,
"verification_uri_complete": "https://idp/mga/sps/oauth/oauth20/user_authorize?user_code=uo1t-ulcs",
"verification_uri": "https://idp/mga/sps/oauth/oauth20/user_authorize",
"expires_in": 299
}
But now, after entering the login, password and confirming the permission (openid), when I try to go to /token or /user_info, I always see this:
{
"error_description": "FBTOAU256E Pending. The user code is not yet verified.",
"error": "authorization_pending"
}
Suggestion from
OAuth: Device Flows - IBM Security Identity and Access
IBM Security Identity and Access |
remove preview |
 |
OAuth: Device Flows - IBM Security Identity and Access |
OAuth: Device Flows Introduction to Device Flows As IOT devices become more prevalent, so does the importance of the way these devices interact with user information and the web. These devices often need to call APIs which require authentication, but cannot provide a suitable method of user interaction in order for traditional authentication mechanisms such as username/password. |
View this on IBM Security Identity and Access > |
|
|
doesn't solve the problem
------------------------------
Sergey Leontev
------------------------------