Вы не вошли. Пожалуйста, войдите или зарегистрируйтесь.
Hi community,
I've been facing a challenge with token limitations while developing a mobile application for real-time tracking of units using Wialon's API. To ensure scalability, each user logging into the app needs to utilize their own token to avoid hitting the 1000 token limit. Could someone please provide guidance on how to tackle this issue?
detroithitec hello, could you please, specify what kind of issue you've faced with during the creation of tokens for the users?
Thank you for reaching out. In our application architecture, we aim to have each user logging in to utilize their own token to ensure scalability and prevent token conflicts among users. So If each user's login generates a token, we will quickly exhaust the 1000-token limit allocated to our account.
detroithitec hello, the 1000 tokens limits applies to the user, not account -- The number of tokens per user is limited by one thousand
You can also set fixed duration for the tokens. For example, default duration is 30 days. So, token will expire in 30 days. In your case, you can set it with less duration period.
If you mean something else, please, provide us more details or write to support@wialon.com
Hello, following our recent discussions, I have implemented a solution for token management that involves storing tokens in our database. This approach has proven effective in ensuring scalability and minimizing token conflicts among users.
However, a new concern has surfaced regarding password synchronization between our application and the Wialon web interface. While wialon's API facilitates password updates from our application to the web interface, I am interested in exploring bidirectional synchronization capabilities.
Specifically, if a user updates their password via the Wialon web interface, is there a way for our application to receive this updated password simultaneously?
Best regards,
