HighQ APIs support OAuth 2.0 with refresh tokens, where a new access token and refresh token are issued during each authentication cycle.
My question is about the limits of refresh token rotation in HighQ:
-
How many times can we continue to use the refresh token process before user interaction is required?
-
Is there a maximum rotation count or expiry policy specific to HighQ?
For context, Microsoft’s implementation allows refresh tokens to be rotated up to 90 times before requiring user sign‑in again. I’d like to understand what the equivalent limits are in HighQ?