- Joined
- Feb 6, 2018
- Messages
- 11,248
- Reaction score
- 7,110
Hi,
We discovered what seems to be a bug in v20u3 (also U4) where the TEST feature of the CRM page breaks authorization if a CRM, like Dynamics, uses a new RefreshToken when getting a new Access Token. It seems to affect any CRM that receives a new refresh token when running the Auth scenario.
If we use the TEST feature, it works once then it breaks since it didn't update the refresh token properly. If we don't touch it tho, it works properly in the background and gets refreshed correctly.
We have tested with Dynamics and our custom Bullhorn template.
We discovered what seems to be a bug in v20u3 (also U4) where the TEST feature of the CRM page breaks authorization if a CRM, like Dynamics, uses a new RefreshToken when getting a new Access Token. It seems to affect any CRM that receives a new refresh token when running the Auth scenario.
If we use the TEST feature, it works once then it breaks since it didn't update the refresh token properly. If we don't touch it tho, it works properly in the background and gets refreshed correctly.
We have tested with Dynamics and our custom Bullhorn template.