Close popover
Manuel Herias Gomez (HERIM)
Principal System Architect - Pega Consulting
Pegasystems Inc.
HERIM Member since 2010 8 posts
Posted: March 8, 2017
Last activity: March 14, 2017

Refresh token is truncated

Hi All,

We recently migrated onto 7.2.2 version. When authenticating using OAuth2 with grant type authorization code, we get a warning regarding the refresh token being truncated because exceeds the length in the DB (512). Now, when making subsequent requests we get an error in the response because of the refresh token not being correct. I have seen that the access token column length in DB is set to 4000, why the refresh token is set to be max 512? Could anyone let us know if this is a bug or is correct as per any OAuth2 spec? I have not found anything about this.

The following is the warn message I can see when accessing the protected resource, the first time :

"Property pyRefreshToken has been truncated in its database column; the maximum column length is 512 but the property (length 1144) has ..."

Thanks a lot!

Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.