Selecting a Migration Option

You can migrate secrets by using one or more of the options illustrated in the following figure:


Options in the SecretStore conversion utility

You can convert secrets before or after installing SecureLogin 3.0. However, we recommend that you convert before uninstalling Novell Single Sign-on 2.1. Entlist.ini and applist.ini must be in specific locations so that ss21cvt.exe can locate these files. If you run ss21cvt.exe before you uninstall NSSO 2.1, you don't have to manually place the two .ini files.


Overwriting Secrets

The first option is to convert v-GO for NSSO 2.1 secrets to SecretStore 3.0 format. To use this option, check the Convert check box, but don't check the Overwrite check box.

If you don't check the Overwrite check box, and if a 3.0 secrets exists, NSSO 2.1 secrets don't overwrite SecretStore 3.0 secrets.

Scenario: Convert is Enabled but Override is Disabled

Rie is a user at Digital Airlines, which has been using Novell Single Sign-on 2.1. You install SecureLogin 3.0. Rie uses 3.0 to log in to Web sites. As the following table illustrates, secrets for both 2.1 and 3.0 for Rie exist in eDirectory.

Secret and Date Secret and Date Results during a Migration

2.1a, created October 1

3.0 a, created September 1

No change

2.1b, created October 1

3.0 b, created September 1

No change

2.1c, created October 1

 

2.1c becomes 3.0c

You run the conversion program. Because secrets 3.0a and 3.0b exist, Rie's secrets 2.1a and 2.1b are not converted to 3.0 format. Secret 3.0c does not exist. Therefore, the conversion program converts 2.1c to 3.0 format and writes it as 3.0c.


Converting and Overwriting Secrets

The second option is to convert NSSO 2.1 secrets and overwrite SecretStore 3.0 secrets. To use this option, check both the Convert check box and the Overwrite check box.

You can't overwrite secrets without converting them. If you enable Overwrite, the conversion program only overwrites secrets that have earlier dates. The 2.1 secrets that have a later date than 3.0 secrets overwrite the older 3.0 secrets during the conversion process.

Scenario: Convert and Overwrite Are Both Enabled

Claire works at the VMP company, which has been using Novell Single Sign-on 2.1. You install SecureLogin 3.0. Claire uses 3.0 to log in to Web sites. As the following table illustrates, secrets for both 2.1 and 3.0 for Claire exist.

You run the conversion program. Because Secret 2.1a is newer than Secret 3.0a, the program converts Secret 2.1a to SecretStore 3.0 format and overwrites 3.0a.

Secret and Date Secret and Date Result during a Migration

2.1a, created October 1

3.0a, created September 1

3.0a is overwritten

2.1b, created October 1

3.0b, created November 1

2.1b is not converted

2.1c, created October 1

 

2.1c becomes 3.0c

Secret 2.1a is older than Secret 3.0b. The program does not convert 2.1b to 3.0 format. Secret 3.0b is not overwritten.

Because 3.0c does not exist, the conversion program converts 2.1c to 3.0 format and writes it as 3.0c.


Removing Secrets

The third option is to remove NSSO 2.1 secrets. To do this, check the Remove check box.

If you select both 'Convert and Remove, the conversion program first tries to convert 2.1 secrets to 3.0 secrets. It then removes the 2.1 secrets.

If you select Remove but do not select Convert, the conversion program only removes Novell Single Sign-on 2.1 secrets. It does not delete connector secrets or secrets owned by other services.