Successfully fetched access token and ID token using authCode
Validating ID token received from access token end point
JWT is signed
Successfully validated ID token with standard claims
Fetch Operator
trying to fetch operator from DB
Successfully established operator from received ID token claims
However we are trying to get the Access Token and the ID Token to use it for communication with other systems.
In the logs we managed to see the Token ID in the OIDCClientHandler logger, but the Access Token is shown as ***** when enabling the debug mode on client.oauth2.OAuth2ClientImpl.
Nevertheless we couldn’t find anything related to the retrieval of the Token from the Authentication service to the Clipboard.
Anyone have any input on how to get this token that was printed in the log?
@MohamadShokor Just a quick follow up - did you ever get a response or figure this out? I am in the same situation with PRPC 8.6 and I would like to use that access token as well. The log files in my case just state the application has successfully received the access token.
@SReddyR87 AccessTokens are instances of Data-Admin-Security-OAuth2-AccessToken and are saved in DB. Look at the java step in OOTB activity GetOperatorAccessToken to retrieve the AccessToken.
@MohamadShokor No record appears in Data-Admin-Security-AccessTokenKeys when I login via OIDC. I see D_pyOIDCLoginInfo contains the ID token but it is not refreshed when the token expires. I have created SR for this.
@EngincanY I did not really dig into the refresh token flow, as It was just proof of concept. But please update this thread with a solution for the refresh token if the SR lead to some help.
Please check if your OIDC Provider uses this one NimbusOIDCClientHandler. In that case, you can enable debug logger on the same. Please refer to the above article (during the end of the video you would notice the ID token). Hope that helps."