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.9.2 Creating Audit V2 Tables in an Existing Database

1.
In the Administration Tools window, click Install Audit V2 Server.
Click Create audit database tables in an existing database server.
Click Next.
If this password is modified, you must modify the Audit V2 connection parameters by following the procedure explained in 3.9.3, "Setting up the Connection to the Local Audit Database".
Click Next.
If you create the audit V2 tables in an existing MySQL database, the connection to the Quest ESSO Controller is also set up by the wizard: the Quest ESSO local audit database is operational when the wizard completes.
If the existing database installed on the
Quest ESSO Controller is not a MySQL database, or if you want to set up the connection through the local OLE DB and/or ODBC driver, you must set up the connection parameters as detailed in 3.9.3, "Setting up the Connection to the Local Audit Database".

3.9.3 Setting up the Connection to the Local Audit Database

All audit events received by the Quest ESSO Controller are stored in the local audit database. This section describes how to set up the link between the Quest ESSO Controller and the local audit database.
1.
In the Administration Tools window, click Configure local audit database.
a)
To set up connection parameters with a Microsoft SQL Server database:
Click Use Quest ESSO embedded database and enter the administrator's password, as shown below:
Click the Advanced button to set a specific instance (if SQL Server is not installed on the Quest ESSO Controller) and administrator's name (optional):
Click Apply.
b)
To set up connection parameters with a database server (MySQL, Microsoft SQL Server, PostgreSQL or Oracle) through the local OLE DB and/or ODBC driver:
Click Use existing corporate database and click the  button to fill-in the Connection string field.
Select in Table name drop-down list the proper audit table.
Click the Verify button to check the configuration settings.
Click Apply.
3.
If necessary, restart Quest ESSO Security Services to take configuration changes into account.

3.9.4 Updating the Audit Translation Data

1.
In the Administration Tools window, click Update Audit translation data.
The Insert/Update Audit MetaData window appears.
Errors column: the list of available translations of errors found in the selected folder, for the selected category.
Resources column: the list of available translations of resources (type, attribute, known values of objects appearing in audit events) found in the selected folder, for the selected category.
4.
Click Import.

3.10 Declaring the Technical Accounts Used by the Quest ESSO Controllers

1.
In the Administration Tools window, click Configure Directory and Audit login/password.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating