Hi Smita ,
When a user logs in to the application using OIDC, the Identity Provider (IdP) issues an ID Token, Access Token, and optionally a Refresh Token.
Pega creates a unique cache key based on the combination of Client ID , Scopes , User and Grant Type and stores the issued tokens against that key.
Later, when an outbound call is made using the same Client ID and Scopes, Pega first looks up the cache (or database) using the generated key.
If a matching entry is found, Pega fetches the associated access token and
- If the access token is still valid, it is reused for the outbound call.
- If the access token has expired, Pega checks for a valid refresh token and uses it to obtain a new access token from the IdP.
Important Note :
To enable automatic token renewal, the “Use refresh token if available” option must be enabled in the Authentication Profile
Make sure the order of scopes provided must match between Authentication service and Authentication Profile .
This entire process is handled automatically by Pega behind the scenes and does not require any custom implementation.