AceBIT

1) Re-opening a server based password file in RW mode does not work.

2) After loosing network connection (eg: disabling the network adapter and then re-enabling) the client session lingers and thus the client is unable to re-logon to the depot server until an administrator manually disconnect the old session using the server console. A connection time-out/heartbeat would provide some benefits.

3) There should be a Deport Server's administrator role so each different administrator user should be granted admin rights on (and only) their specific password file and thus provide granular user-access control to each file.

4) We've found some users getting scrambled (probably encrypted or badly uncrypted) passwords.

Server running version 3.0.5
Client running version 3.1.6.0

Hello,

1.) Can you please tell us what you are doing exactly here? What are your steps in detail?

2.) Normally a disconnected session is deteted almost instantly. Connection timeout is a system wide default parameter - 60 seconds.
Probably you mean users stay "locked" on server, not "connected"?

3.) Alright, thanks for your suggestion, we will forward this to the responsible product manager.

4.) Please make sure these clients all use the most current version of the Password Depot 3 Client. Since version 3.1.4, passwords are encrypted inside the password file as well.

________________________
Best regards
Mirko - AceBIT - Support

1) Using the "Open List.." w/o closing the file clearing the "read-only" checkbox

2) No I do mean "connected". Session lingers and the server console clears the IP but the state tab keeps showing "connected" and no client session can be established until the administrator manually disconnect the session.

4) They are all running the last version. I'll keep an eye on that.

Hello,

1.) When you open a file read-only, and then decide to make some changes, it wont work just to open file again via "File" -> "Open list" and just to deactivate the "Read-only" option. You have to close the file here at first via "File" -> "Close file" and then reopen it the normal way - this time without the "Read-only" option. We already forwarded this to the responsible product manager, since we are not sure if this is normal or a bug. If its a bug, this will be corrected in one of the next updates.

2.) Allright, we will report this and will contact you again as soon as we get any answers.

______________________
Best regards
Mirko - AceBIT - Support

Let me know when you have any new on this issue..

cheers...