Steps to replicate the issue (include links if applicable):

• Obtain refresh_token using /v1/login API
• Trigger /v1/token-refresh API more than 5 times

What happens?:
See that although your refresh token is still valid you are getting 403 response.

What should have happened instead?:
You should get a valid access token.

Notes
This is happening due to limitations on max amount of access tokens per refresh token we have put in place. We need to consider either changing the logic or updating the max amount of access tokens per refresh token. Also we should add an expiration date for the cache entries that are counting access tokens.

Also need to consider whether we should update the v1 API as well with this fix.