5/13/2012 6:15:08 AM
 Alain B Posts: 9
|
Hi, We are using Desktop Client since several weeks now. We appreciate it a lot, however, several points need clarification and/or enhancement.
How is maintained the cache content ? Is it automatic when Desktop Client can contact the server / fully manual / when secret is used / ... ? What are the exact functions of Refresh List Cache, Clear all cached data, Cache all Secrets ?
The messages displayed by Desktop Client may not be very clear.
Your token has expired ( What does this means ? What should the user do ?
java.net.UnknownHostException:... when trying to open secret that, I suppose, is not in cache and server is unreachable.
A Desktop Client User Guide can be helpful. Do you plan to provide such guide ? Don you plan to enhance information / error message ?
Thanks a lot for your help.
|
|
|
0
• link
|
5/15/2012 12:33:06 PM
 david c Administrator Posts: 22
|
Hi Alain,
Caching: -Cache content is stored in encrypted files in the same folder as the executable. These files are machine specific, so you can not copy them to another computer and open them in the application on another computer
-Caching is automatic when editing a secret, opening one that is not in the cache, or when the list is not in the cache.
Refresh List Cache: - Caches the Folders, Favorites, and the main list of Secrets (the same data that is displayed on the Secret list on dashboard - Secret names, folders, and templates)
Clear All cached data: - Clears the Secrets data (field values) cache
Cache All Secrets: - Goes to the server and 'opens' each secret and gets the cache of all the data for that secret. There will be an audit record for each one. Secrets that are already cached will not be cached again, if you want a full refresh, click clear all first.
Token expired: - This is related to the 'Remember Me' setting in Secret Server. Upon receiving the error the user should log out and back into the desktop client.
UnknownHostException:... - Correct. Trying to access the server because the Secret is not in the cache, and can not hit it.
We are planning on a User Guide, as well as some enhancements to error messages and general usability.
-- -- Secret Server Development Team
|
|
|
0
• link
|
5/21/2012 2:32:22 AM
 Alain B Posts: 9
|
Hi David,
Thanks a lot for the explanations; now caching is clear for me.
I have remaining questions about token. I am writing a quick startup guide for our users and I want to be sure to fully understand Desktop Client processes.
Is the token refreshed automatically each time Desktop Client contacts the server ? or the user has to re authenticate anyway after expiration period ?
From the user view point the first option is better: he only has to periodically to launch Desktop Client when the server is reachable. With the second option the user must enforce re authentication manually when the server is reachable: this is not very easy to manage.
In both cases the token may expire when the server is unreachable without any warning to the user . This may happen even for frequently used Secrets and generate negative opinions (
Cosmetic changes on information-error messages can also help a lot obtaining user strong positive opinion.
|
|
|
0
• link
|
5/21/2012 6:41:55 PM
 Ben Posts: 94
|
Hi Alain,
The token for the clients is not a sliding window, so the token does not get automatically refreshed based on activity.
The Remember Me setting determines the length of the window during which the user will not need to re-authenticate after initially logging into the desktop client.
-Ben
-- Thycotic Development Team
|
|
|
0
• link
|