Node SDK 401 after refresh with clock skew

Hit a wall with the Node SDK auth flow. Token refresh succeeds via POST /oauth/token, but the immediate next GET /api/v2/users/me throws 401. Checked the JWT payload and the iat is 300s ahead of the server clock. The SDK’s internal clock check rejects it before sending.

{
 "error": "invalid_grant",
 "error_description": "Access token expired or invalid"
}

Is there a way to inject a custom clock offset or disable the strict exp check in the PlatformClient instance? setAuth seems to just swap the token string without touching the validation logic.