My client uses OAuth 2 with OpenID connect token and I am wondering if we have OOTB support for it.
We have version 7.2.1 and I can connect through standard OAuth 2 but only get the Access Token, and not the token_id with the information we need. I have been able to have a workaround, but could not have this working OOTB.
The redirect service, performs a post in a java step, and retrieves just the Access Token :
As I suspected, we don't support OOTB OpenID Connect. I can see the whole token content in Base64 encoded, when using a Connect-HTTP in the redirect REST service (prior to the Java step that performs a POST in order to request the Access token). The response I get through the Connect-HTTP is correct and contains the Access Token and Token_Id. If using OOTB we just get the Access token.
Many thanks for your reply! I did suspect that, but just wanted to confirm.
We use authorization code grant and the client uses OpenID, we just receive the Access Token, but we don't parse the rest, despite being sent (I have tested with postman and also with a Connect-HTTP mapping the response to the Clipboard).
Do you know if there is any plan to have support in the roadmap?
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.