7.4 Running SecureLogin 6.0 SP1 in Mixed Environments
You can run SecureLogin 6.0 SP1 and SecureLogin 6.0 in the same environment.
When SecureLogin 6.0 SP1 runs in the same environment as SecureLogin 3.0.x, SecureLogin 6.0 SP1 does the following:
-
Versions the SecureLogin data store.
-
Saves SecureLogin 6.0 SP1 data in the SecureLogin 6.0 data format.
This mixed mode enables you to gradually deploy SecureLogin 6.0 SP1 in a SecureLogin 6.0 environment while still allowing you to perform most administration tasks during the transition.
Deploying SecureLogin 6.0 SP1 in a mixed environment has the following limitations:
-
Limited administrative functionality
When you run SecureLogin 6.0 SP1 in mixed mode, new features such as shadow variables will not work. Also, some SecureLogin 6.0 SP1 settings and changing script descriptions aren’t supported in mixed mode.
-
Warning messages
To inform you that you are running in mixed mode, a warning message is displayed when data is saved in the SecureLogin 3.0 format.
7.4.1 Upgrading to SecureLogin 6.0 SP1
The single sign-on functionality of SecureLogin uses the directory schema to determine which version of the data store to write out. If this functionality finds the new directory attributes that are added by the SecureLogin 6.0 SP1 schema tool, SecureLogin uses the new data format.
In mixed environments, SecureLogin 6.0 SP1 reads and writes data in the SecureLogin 3.0 format and functions as usual. No administrative intervention is required.
When workstations are upgraded to SecureLogin 6.0 SP1, they continue to use the SecureLogin 3.0 data format on the User objects. This functionality allows users to move between SecureLogin 3.0 and SecureLogin 6.0 SP1 workstations.
After all users in the tree have been upgraded to SecureLogin 6.0 SP1, you can run the schema extension tool and upgrade the directory schema. All SecureLogin clients will then upgrade their data stores to the SecureLogin 6.0 SP1 format.
If any SecureLogin clients remain in the tree after the schema has been updated to include the SecureLogin 6.0 SP1 attributes, the SecureLogin 3.0 clients will receive the "corrupt data" error message.
After the directory schema has been extend for SecureLogin 6.0 SP1, it is not possible to revert to the SecureLogin 3.0 data format.
7.4.2 Managing Mixed Environments
While SecureLogin is running in mixed mode, you will be able to modify most of the corporate and user configuration settings. However, if you attempt to set a new setting, SecureLogin displays the following warning message:
SecureLogin was unable to save some of your data because it is not supported by the currently selected data format version. This incompatible data has not been saved.
The incompatible data is any new setting that appears in SecureLogin 6.0 SP1 but was not present in SecureLogin 3.0. Incompatible data could come from the following:
-
Dialog position information
-
New settings
-
Shadow variables