We are getting an issue with refresh token on the mileston server.
The stack trace doesn’t reveal what is causing the exception in your code.
I suggest that you debug the situation. In order to do this efficiently you can shorten the duration of the token, making the token refresh happen sooner. Use the information in this knowledge base article to lower the “ClientTokenTimoutMinutes”.
https://supportcommunity.milestonesys.com/KBRedir?art=000032987&lang=en_US
Thanks for your response. I have added more minutes about the clientTokenTimeoutMinutes variable and we haven’t had problems.
I must emphasize that this is not my recommendation. My advice is to lower the token timeout and debug the integration solution. Extending the token timeout to avoid renewal is not a viable long-term solution.
Hi @Bo Ellegård Andersen (Milestone Systems) , the system is on production server and if we perform it then the integration will be offline some minutes. Could you reproduce it on laboratory???.
I do not have information on what your integration is doing; the stack trace only indicates that a token refresh is being attempted. This means I do not have information that allows me to try to reproduce.
An alternative approach is to implement logging in your solution. This will allow you to gather more information from the system running at your customer’s site, eliminating the need for your own test setup, although that is what I would recommend.
When you say you haven’t had problems, is it because you extended the token timeout significantly, preventing the issue from occurring, or did you extend it slightly, resulting in less frequent renewals that seem to work without causing issues?
If it is the latter, it might be acceptable. However, identifying the root cause of the issue through debugging would be more satisfying.
Yes, we’ve extended the token timeout. So far we have it controlled. My concern right now is about the export that I created another ticket. Please, help us about that.