The LDAP option installs SecureLogin into an LDAP environment with eDirectory.
You can specify more than one LDAP server for the SecureLogin installation. Although the dialog box in the installation program allows you to specify only three LDAP servers, you can specify additional servers by modifying the responsefile.ini file.
The LDAP option does not require Client for Open Enterprise Server for Windows. However, if Client for Open Enterprise Server is installed on the workstation, Client for Open Enterprise Server is the initial authentication or Credential Provider. If you want LDAP authentication to be the initial authenticator, you must uninstall Client for Open Enterprise Server.
Log in to the workstation as an administrator.
Run the NetIQSecureLogin.exe file.
Accept the license agreement and click Next.
Select NetIQ eDirectory with LDAP as the datastore.
Click Next.
Click Install.
Click Next.
In the Custom Setup window, select the features you want to install.
Click Next.
In the LDAP Server Information window, specify the server address, port and the root CA certificate path.
NOTE:SecureLogin supports the following certificate formats:
BASE64 (*.b64)
PEM (*.pem)
IMPORTANT:It is mandatory to specify the root CA certificate path when installing SecureLogin in the LDAP mode. Specifying the root CA certificate is also mandatory when migrating to the LDAP mode using slMigrationHelper.exe. Although it is not recommended, but if you do not wish to specify the root CA certificate path, see Installing SecureLogin in the LDAP Mode Without Root CA Certificate to install SecureLogin without a certificate.
WARNING:Installing SecureLogin without a root CA certificate makes SecureLogin and the LDAP server open to security threats. It is not recommended to install SecureLogin without the root CA certificate.
Perform one of the following methods to install SecureLogin in the LDAP mode without the root CA certificate.
Perform the following steps to install the SecureLogin in the LDAP mode without the root CA certificate:
Log in as an administrator.
Launch the command prompt.
Navigate to the location where the SecureLogin installer package is saved.
Run the NetIQSecureLogin.exe installer file with the INSTALLWITHOUTCACERT=Yes parameter. For example:
NetIQSecureLogin.exe INSTALLWITHOUTCACERT=Yes
NOTE:You can use the INSTALLWITHOUTCACERT=Yes parameter and continue the remaining installation with the GUI installer. For example, NetIQSecureLogin.exe /install INSTALLWITHOUTCACERT=Yes.
Perform the following steps to modify the registries. The registry modification is necessary to prevents SecureLogin to check for root CA certificate.
Click Start > Run to open the Run dialog box.
Specify regedit and click OK to open Registry Editor.
Navigate to the HKEY_LOCAL_MACHINE > SOFTWARE > Novell > Login > LDAP key.
Right click and click New > DWORD.
Rename the DWORD to CACertNotProvided.
Edit the CACertNotProvided value to 1.
For more information, see Section 9.0, Installing through the Command Line.
IMPORTANT:Upgrading SecureLogin using the responsefile.ini file is not supported.
Perform the following steps to install the SecureLogin in the LDAP mode without the root CA certificate using the responsefile.ini file:
Log in as an administrator.
Specify INSTALLWITHOUTCACERT=YES in the responsefile.ini file.
Launch the command prompt.
Navigate to the location where the SecureLogin installer package is saved.
To install SecureLogin on all the target machines with the responsefile.ini file, run the following command.
NetIQSecureLogin.exe /install X_PRIMARYSTORE=LDAP PATHTOISS="c:\temp\responsefile.ini" /quiet
Perform the following steps to modify the registries. The registry modification is necessary to prevents SecureLogin to check for root CA certificate.
Click Start > Run to open the Run dialog box.
Specify regedit and click OK to open Registry Editor.
Navigate to the HKEY_LOCAL_MACHINE > SOFTWARE > Novell > Login > LDAP key.
Right click and click New > DWORD.
Rename the DWORD to CACertNotProvided.
Edit the CACertNotProvided value to 1.
For more information, see Installing SecureLogin Using The Responsefile.ini File.
WARNING:Installing SecureLogin with TLS 1.1 is less secure than using TLS 1.2. It can open your deployment environment to security threats.
Perform the following steps to modify the registries. The registry modification is necessary to enable TLS 1.1 in SecureLogin.
Click Start > Run to open the Run dialog box.
Specify regedit and click OK to open Registry Editor.
Navigate to the HKEY_LOCAL_MACHINE > SOFTWARE > Protocom > SecureLogin key.
Right-click and click New > DWORD.
Rename the DWORD to AllowTLSv1.1.
Edit the AllowTLSv1.1 value to 1.