Refresh token becames Invalid

Hi Vladimir,

This Session duration on Sugar 7 blog post that I wrote a while back should give you a full picture on how it all fits together and most of the client/server side possible causes.

Hope it helps

Vladimir, did you get an answer to this?
My experience is that :
-you login to get a set of tokens
-the access token expires after an hour
-you use the refresh_token to get a new access_token, and it sends back a new refresh_token as well
-as of this point the original refresh_token is invalid

This means that if I have several microservices deployed (or even the same one scaled to 4 instances) the first one of them to refresh the token can continue, and the others fail thereafter.

This question has been asked here a number of times and never answered to the best of my knowledge
wcn

Vladimir, did you get an answer to this?
My experience is that :
-you login to get a set of tokens
-the access token expires after an hour
-you use the refresh_token to get a new access_token, and it sends back a new refresh_token as well
-as of this point the original refresh_token is invalid

This means that if I have several microservices deployed (or even the same one scaled to 4 instances) the first one of them to refresh the token can continue, and the others fail thereafter.

This question has been asked here a number of times and never answered to the best of my knowledge
wcn

Hi Wendell,

I'd recommend that each of these microservices use a unique platform ID which would allow each of them to have their own access tokens and refresh tokens.

How platform parameter works in Sugar v10 REST API « Sugar Developer Blog – SugarCRM 

Obviously, I understand that with scaling you could have any number of microservice instances connecting to Sugar which could make registering platforms problematic. Is it possible that you could deploy a gateway service that manages communication with Sugar from a single point?