Question
#
FR
Last activity: 27 Mar 2024 6:15 EDT
Pega / Google Oauth 2.0
Hello,
i want to integrate google api's and i have created an authentication profile(with credentials from google cloud )
The first connection is good but the refresh token does not work
any idea?
i saw this article https://support.pega.com/question/refresh-token-not-working-integrating-google-api-using-oauth-20
my pega version is higher than 8.3 and the bug still same
Accepted Solution
Updated: 27 Mar 2024 6:15 EDT
Maantic Inc
IN
This is a known issue in Pega, actually the refresh token is not persisted in Data-Admin-Security-OAuth2-AccessToken and for this reason we face the issue.
Alternatively we have created a separate REST connector to retrieve the access token using refresh token and we managed to store the refresh token in a DSS rule. Use the same refresh token to generate the bearer token. Once you get the bearer token use it into your first integration to suffice the requirement.
Just a point to remember for the first invocation the grant_type will be authorization_code and from the next time it will be refresh_token.
Maantic Inc
IN
So how this can be addressed is two fold api call . so basically Oauth is another api call which fetches bearer token in return.
What I suggest is create a rest for that and store the bearer token in node level data page.
Secondly when you do the actual endpoint REST call pass it under auth headers tag it should work fine.
I faced the same when consuming google API's did the same it does'nt refresh when you configure automatically using auth profile.. Be sure to flush data page based on token expiration which will be part of the initial token response generally its 3600 seconds or 1hr just check it.
Try it am absolutely sure it will worked I used it for Google Fitness API.
Accepted Solution
Updated: 27 Mar 2024 6:15 EDT
Maantic Inc
IN
This is a known issue in Pega, actually the refresh token is not persisted in Data-Admin-Security-OAuth2-AccessToken and for this reason we face the issue.
Alternatively we have created a separate REST connector to retrieve the access token using refresh token and we managed to store the refresh token in a DSS rule. Use the same refresh token to generate the bearer token. Once you get the bearer token use it into your first integration to suffice the requirement.
Just a point to remember for the first invocation the grant_type will be authorization_code and from the next time it will be refresh_token.