Clarification on OAuth 2.0 Token Mechanism at Runtime

General
, , ,
1

Hi there,

I’m working on implementing OAuth 2.0 in my personal application, but after reviewing several articles, I still haven’t found a clear explanation. Could someone help me understand how token mechanisms work at runtime?

Thanks in advance!

2

Hi ,

When we provide the authentication profile to Connect-REST, Pega generates an access token, which is then stored in the Data-Admin-Security-OAuth2-AccessToken class.

The next time Pega attempts to use the authentication profile, it first checks if there is an active access token available. If a valid token exists, it will use that token. Otherwise, it will generate a new token and store it in the access token table.

Let me know if you need any additional details or clarification on this process.