to get a personalized navigation.
to get a personalized navigation.
Hello,
We are migrating from VNI to Visma Connect Authentication. In our product, a user needs to log in to Visma.net so we can save a token in database, that we can then use to make calls to the Visma.net API while the user is offline.
We have a problem when the user sets up multiple configurations in our app, with each configuration targeting a different tenant. With VNI, we used to store for each configuration the token along with the company ID. With Visma Connect, here is what we observe:
=> From that point on, the refresh token for configuration #1 cannot be used anymore, we get back an invalid_grant response when trying to obtain a new access token.
Changing the application settings so a refresh token can be re-used does not solve the problem. Refresh tokens per user is set to 5. The only way to make our product usable is to ask our users to log out from Visma before they set up a new configuration, or create the new configuration in a separate browser.
Is it by design that when a refresh token is created all the refresh tokens created during the same session are revoked? What can we do to solve this issue?
Thank you for your help.
Solved! Go to Solution.
Copyright © 2022 Visma.com. All rights reserved.