SecureLogin is backward compatible, so all workstations running previous versions continue to operate successfully after the directory is upgraded to the new version. Although the directory is upgraded, the SecureLogin client on the workstation continues to function as the old version of SecureLogin until you have upgraded all users to the new version and manually set the directory database version to the new version.
NOTE:The new features of SecureLogin are not available to users who have not upgraded their client versions.
You can configure directory database versions at the user object, container, and organizational unit levels. We recommend that you set the database version at the container and organizational unit levels. This helps you manage the database and minimize the possibility of conflicting versions.
NOTE:To utilize the SecureLogin 6.0 features such as the storage of single sign-on credentials on the user’s smart card, encryption of the data store using PKI-based credentials, and the AES encryption algorithm support, the data store mode must be set to version 6.0.
To change the data store version:
Launch SLManager.
Select Advanced Settings > Datastore.
In Select Version, select the required version.
You cannot select a version earlier than your current version.
Click Apply. When the upgrade is installed on all workstations, follow this same procedure to change the directory database version. The next time the directory server and the workstation caches are synchronized, SecureLogin operates in the new version mode.