Because Novell SecureLogin 2.5 didn't use SecretStore, you don't have to run the conversion utility when you upgrade to SecureLogin 3.0. SecureLogin 3.0 automatically upgrades a 2.5 cache and upgrades 2.5 directory attributes.
Installers could deploy SecureLogin 2.5 to run in standalone mode or with eDirectory. Even if SecureLogin 2.5 was deployed to work with eDirectory, a cache most likely exists on the workstation, unless the administrator turned that capability off. SecureLogin 3.0 recognizes the cache left by SecureLogin 2.5 and automatically works with it.
If all SecureLogin 2.5 data was stored in eDirectory, and if SecureLogin 3.0 is installed to work with SecretStore, SecureLogin 3.0 is able to use the data from SecureLogin 2.5. Usage occurs because SecureLogin 3.0 still uses the Prot:* attributes in the directory, even if deployed to use SecretStore.
To migrate from SecureLogin 2.5:
While running setup.exe, select to uninstall SecureLogin 2.5 from the workstation.
Install SecureLogin 3.0.