2.3 Updating the Datastore Objects

SecureLogin 6.0 introduced a range of security features, including storing the single sign-on credentials on the user’s smart card, encrypting the datastore by using the Public Key Infrastructure (PKI)-based credentials and the Advanced Encryption Standard (AES) encryption algorithm support.

To support the new features, you must change the SecureLogin 6.0 datastore format.

The SecureLogin 6.0 client can read data created by all the previous versions of SecureLogin. However, the older versions cannot read the data created by version 6.0 and later. In case of a mixed corporate environment where some workstations are running SecureLogin 6.0, 6.1, or 7.0, and other workstations are running previous versions, data compatibility issues arise when a user moves between different versions of SecureLogin on different workstations. This is particularly problematic in Citrix environments or in large enterprise deployments.

If SecureLogin 3.5 is present when you install SecureLogin 7.0, it detects that version 3.5 data is in use and continues to function correctly. In this mode, version 3.5 functions are available. However, any new function that relies on version 7.0 data, is not available.

If you require the new functions, complete the following processes:

  1. Choose a section of the tree to upgrade.

    For example:

    • Container

    • Group

    • Organization

    • User

  2. Make sure that all user workstations in that section of the tree are upgraded with the SecureLogin 7.0 client.

The next time the users log in, their data is converted to version 7.0 format and the new functions are available.