The following procedures apply to the standard configuration of a server managed through an administration workstation. It also applies if your configuration does not separate the server from the administration workstation.
In Active Directory’s MMC, the current datastore version (displayed in the Advanced Settings page) might not update immediately when the directory database version is changed. To update, click OK, then exit the MMC Properties dialog box.
Ensure that you meet the hardware and software requirements listed in NetIQ SecureLogin System Requirements
.
A minimum of 128 MB is required in the Windows directory. An additional 55 MB is required for temporary files, which is deleted after installation is complete.
You must have administrator-level access to the server and the administration workstations.
Back up the existing directory.
You must install Java 1.7 or 1.8 to enable single sign-on to Java applications on the workstation.
For multiple-directory environments:
Identify the domain controller to determine the directory where you will install SecureLogin and the order of replication.
Have access to the domain controller.
The following information applies to the configuration of a server in a Microsoft Windows Server 2003 or Windows Server 2008 operating system environment.
By default, Microsoft Windows Server 2008 and 2012 install the Internet Explorer Enhanced Security Configuration, which is designed to decrease the exposure of enterprise servers to potential attacks that might occur through the Web content and application scripts.
If you are using Internet Explorer, some websites might not perform as expected when SecureLogin is installed. Add-ons and Browser Help Objects (BHOs), such as SSO might not be fully functional.
For more information, see the Microsoft Support Web site for knowledge base article 815141.
To enable single sign-on for Internet Explorer, disable the Microsoft’s Internet Explorer Enhanced Security Configuration before deploying SecureLogin.
You can do this by:
On both Windows Server 2008: Go to Internet Options > Advanced > Browsing, then select the Enable Third party web browser extension (requires restart) option.
In Internet Explorer 8: Open Internet Explorer, go to Tools > Internet Options > Advanced > under Browsing section, select Enable third party web browser extensions option.
After SecureLogin is installed, open Internet Explorer, go to Tools > Manage Add-ons > Tools and Extensions and check if the SecureLogin IE SSO Helper object Class entry is displayed as Enabled.
Uninstall any SecureLogin version prior to 3.5.x.
Ensure that Microsoft Management Console (MMC) Active Directory plug-ins are installed on the administration workstation.
Extend the directory schema for SecureLogin versions prior to 6.0.
If the application type is enabled for single sign-on, install Citrix or Terminal Services clients.
Install Java 1.7 or 1.8 on the server and workstations, if SSO to Java applications is required.
Install SecureLogin on the administration workstation.
Create test users on the administration workstations.
Define and configure the SecureLogin user environment, including enabling the required applications for single sign-on.
Copy the test users’ configuration to relevant objects.
Install the SecureLogin application on user workstations.
If an error appears during an attempted login immediately after you install SecureLogin on an Active Directory server, click OK in the message, wait for a few minutes, then try again. This error occurs because Active Directory takes time to synchronize. If the error continues, restart the server.
SecureLogin supports Microsoft Active Directory operating in an LDAP environment. There are no additional installation or configuration requirements. The only variation to the install is that you select LDAP and not Microsoft Active Directory as the installation platform. For details, see Extending the LDAP Directory Schema and Assigning Rights on the Server.
SecureLogin supports deployment in an ADAM instance. For more information, see Configuring, Installing, and Deploying In Active Directory Lightweight Directory Services.