-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom rest access server #337
Comments
Hi, There is no document. The protocol is easy. look at this class to find it out However, The simultaneous connections are detected by the device id. If you describe your business, we may add that functionality. |
Thanks for your help. So, I decided to dig a bit deeper and check their session logs. It turns out that they were sharing a token, which is only supposed to be used by two clients, with a bunch of different people. Here is the session log of one of them, for just three hours!
My current proposal is to limit users from connecting with more than two devices per day, regardless of whether the previous device was disconnected or not. This is a temporary solution I suggest. |
Have you specified MaxClientCount when you create the token? Does the new session drop the old ones, or is there a bug? What is your server version? @trudyhood, it looks like the ClientCount log report is wrong by FileAccessServer |
Yes, I've set the client limit when I was creating the token. The new sessions do drop the old ones, but after a few minutes, the old ones connect again (But still only two devices are connected at the same time). The server version is: 2.8.361.0.
|
OK, So the users wouldn't get proper service while using the shard token, and this consequence should prevent them to share it. We also plan to change this strategy and block the new connections instead of dropping the old ones. However, it may lead users to share their tokens and make a user always connected. Anyway, why don't you delete the token? |
"We also plan to change this strategy and block the new connections instead of dropping the old ones." Sure, that's the temporary solution I'll go with. There are many such tokens! I'm in the process of creating an external service that will take care of removing them and notifying their respective owners. |
Merged into #340 |
Is there any documentation available for developing a custom REST access server with additional functionalities, such as restricting connections by DeviceID instead of simultaneous connections? I am interested in creating my own REST access server.
The text was updated successfully, but these errors were encountered: