|
Hello,
In addition to the timeout discussed above, the following would be very efficient:
Problem: - When your network connection drops out and reconnects (Wireless LAN, VPN connections, etc) Password Depot client looses connection to Password Depot Server. When trying to login again with Password Depot Client, you get the "Allready logged in" message and it's impossible to logon to Password Depot Server. - If the user was editing any file in "Change mode" the file is also locked and no one can open the file in change mode.
Feature Request, Solution: - The Password Depot Client is equiped with a "Unique Identifier" (Ex: GUID). The "Unique identifier" is set either during the installation of Password Depot Client, or provided by the Password Depot Server, at each successfull login. - The Password Depot Server keeps track of the logged on users AND from which "Unique id" they are logged on. - When a user has lost connection and tries to logon again, he specifies his username and password as usual. When the Password Depot Server sees that the "user is allready logged on", the server requests the "Unique ID" from the client. IF the "Unique ID" is the same (as recorded at the at the last login), the Password Depot Servern "knows" this is a reconnect from the exact same client and can accept user login immediately. The User does not have to wait for a "timeout". - Please observe that the security is not compromised, since you still have to perform a normal login when doing the reconnect. - This solution could also make it possibly to reconnect to a session with a file in "Change mode".
Best Regards
Mikael koniakowski
|