How the Conversion Tool Works

By default, the conversion tool performs the conversion process for the eDirectory (or earlier versions of NDS) tree that is specified by the primary connection. You can use either of the following options:

Only individual users can read their own secrets. Therefore, it is not possible for the conversion tool to convert secrets for a user that is different than the authenticated user.

So that the conversion tool can map an NSS0 2.1 secret to a shared secret, the tool must know which application the 2.1 secret was created for. Not all of the information needed for mapping the secrets is contained in every NSSO 2.1 secret. Whether or not enough information exists depends on the type of application that the NSSO 2.1 secret exists for.

For example, all of the necessary information exists for Web and user-defined applications. However, not all of the necessary information exists for pre-defined and admin-defined applications. This tool does not convert secrets for mainframe applications.

For the pre-defined and admin-defined applications, the information is contained in two files. The information needed to map the secrets for predefined applications is in the applist.ini file, which is located where NSSO 2.1 is installed. If this file is not found, pre-defined secrets will not be converted.

Information needed to map the secrets for administrator-defined applications is in the entlist.ini file. If the administrator has defined any applications in the directory, ENTLIST.INI is created when NSSO 2.1 starts. If entlist.ini is not found, administrator-defined secrets will not be converted.

The conversion tool searches for applist.ini and entlist.ini in the same directory that the conversion tool is in. Thus it is possible to deploy these files along with this tool if NSSO 2.1 is not currently installed. If the conversion tool doesn't find applist.ini, the tool searches for it where NSSO 2.1 is installed in the Passlogix folder. If the conversion tool doesn't find entlist.ini, the tool searches for it in the Windows directory (or the WINNT directory on NT workstations).

After mapping the secrets, the conversion tool converts the data by extracting the usernames or passwords (or both) from the NSSO 2.1 secrets. The tool then populates corresponding shared secrets with the usernames and passwords.