What is the SecureLogin cache used for?
If the cache has been enabled by the administrator, the offline cache downloads SecureLogin data from the Directory and encrypts and stores it on the hard disk of the local workstation/notebook.
The cache contains SecureLogin configuration information including password policies, user credentials, SSO enabled applications and preferences, and makes it possible for SecureLogin to operate even if the workstation is disconnected from the network.
The SecureLogin data that is read and downloaded includes:
- Application definitions, Password Policies and Preferences that are published in the entire path of the user objectâs Directory Hierarchy. For example, OU=London, DC=acme, DC=com. Note: The Stop Walking Here preference will determine whether SecureLogin will search the entire hierarchy for SecureLogin data or stop searching at a particular OU.
- Application definitions, Password Policies and Preferences that are published via Group Policy objects
- Application definitions, Password Policies and Preferences that are published at the User object level
- Application credentials such as Usernames, Passwords, Domains etc. that are stored against the corresponding User object.
The size of the cache file depends on the number of application definitions (and their size), the number of password policies, any preferences that are set, and the number of credentials that are downloaded.
During testing of SecureLogin version 6, 4 Java, 2 Terminal Emulator, 9 Web and 14 Windows application definitions (including Lotus Notes and SAP), 8 password policies and 19 sets of credentials resulted in a 179KB cache file.