Chat now with support
Chat with Support

Enterprise Single Sign-On 8.0.6 - Installation Guide

1. Overview 2. Preparing the Storage of Security Data in the LDAP Directory
2.1 Active Directory 2.2 Active Directory + ADAM or AD LDS 2.3 OpenLDAP 2.4 Netscape iPlanet / Sun Java System / Red Hat / Fedora Directory Server 2.5 Novell eDirectory 2.6 IBM Tivoli Directory Server 2.7 Deploying a Workstation LDAP User Account
3 Installing Quest ESSO Controllers and Audit Databases 4 Installing and Configuring the Software Modules on the Workstations 5 Enabling the Self Service Password Request (SSPR) Capability 6. Enabling OTP Authentication 7 Enabling the Group Membership Modification Feature 8 Centralizing Parameters Using Group Policy Objects (GPO) 9 Installing Quest ESSO MSI Packages in Silent Mode Appendix A: Advanced Configuration: Audit Appendix B: Activating Traces Appendix C: Retrieving the Serial Number on a MiFARE RFID Badge

3.7 Importing an External Key

This task allows you to import the public key of an external application into the Quest ESSO security directory, in order to allow Quest ESSO users to share their accounts with the external application.
In the Administration Tools window, click Import an external key.
If you are using Active Directory as the Quest ESSO security repository, when the wizard asks you to enter the login/password of an administrator account, use the account who is member of the Domain Admins group and that you have specifically created to install Quest ESSO.

3.8 Importing/Exporting the Controller Key

Before importing or exporting the controller key, make sure Quest ESSO Security Services are started.
In the domain where the primary controller is installed, in the Administration Tools window, click Import/Export controller key.
Select Export server key.
Click the Select button to create the authentication description file and click Ok.
In the domain where the secondary or associated controller is installed, in the Administration Tools window, click Import/Export server key.
Select Import server key.

3.9 Installing and Configuring the Local Audit Database

Quest ESSO provides the Audit V2 Database Server, with advanced filtering capabilities. The installation procedure will differ depending on your needs:
If you want to migrate an existing Quest ESSO Audit database from V1 format to the V2 format, please contact your Quest Software representative
For each Quest ESSO Controller installed, you must setup a Local Audit Database. If several Controllers are installed or if you plan to install several Controllers, these Controllers must share the same master audit database.

3.9.1 Installing the Provided Audit V2 MySQL Database Server

In the Administration Tools window, click Install Audit V2 Server.
Click Install a MySQL database server on this Quest ESSO controller..
Click Next.
The Data folder, Port number and Super user name fields are already filled-in.
In the Super user password and Confirm fields, Type a password for the database super-user that is about to be created.
Click Next.
If you want to modify the displayed data, click the Advanced button to edit the fields.
Click Next.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating