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

A.2 Audited Events

The list of audited events is available on all Quest ESSO Controllers and Clients by opening the Errors and Events tool, available in
Start | Programs | Quest Software | Enterprise SSO | Errors and Events
For more information on this tool, see Quest ESSO Console Administrator Guide.

Appendix B: Activating Traces

Start Registry Editor.
Create the HKEY_LOCAL_MACHINE\SOFTWARE\Enatel\WiseGuard\Debug key.
2 by default.
If you want to trace Password Reset, create the HKEY_LOCAL_MACHINE\SOFTWARE\Enatel\WiseGuard\Framework\ResetPassword key, with the following value:
When the user logs on his/her workstation, the following trace files are created in the specified directory:
WGSSxxxx.log: traces of the Quest ESSO Security Services service.
ssoenginexxxx.log: traces of the SSOWatch engine.
GinaSSOWatch.log: traces of the SSOWatch module GINA.
WGSafeGina and winlogonxxxx.log: Advanced Login traces.
WGConfigxxxx.log: traces of WGConfig.exe, which allows you to configure the Quest ESSO Security Services on the Quest ESSO workstations.
SSOBuilderxxxx.log: traces of Enterprise SSO Studio.
TokenManagerxxxx.log: traces of the Token Manager software module.

Appendix C: Retrieving the Serial Number on a MiFARE RFID Badge

On MiFARE badges, a sector is a set of 4 blocks, each block containing 16 bytes. Reading serial number from sector 1 means reading serial number from block 4.
To locate the serial number in the block of data, a given number of Most Significant Bytes or MSB (the left part of the block) and a given number of Least Significant Bytes or LSB (the right part of the block) are ignored. The remaining middle set of bytes is then written in ASCII to build the serial number. All leading 0 are removed.

C.1 Parameters

the MiFAREBlockNumber registry value is not set or set to 0xFFFFFFFF
the MiFAREBlockNumber is set to a valid value between 0 and 15 inclusive and an error occurs, such as wrong key or configuration
Set the MiFAREBlockNumber to a block number, not a sector number.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating