Product Documentation

Operations

Mar 18, 2011

Single Sign-on logs plug-in or user-generated events in the host computer’s Windows event application log. Events are classified as information, warnings, or errors. Warning and error events are always logged. Logging of information events is disabled by default, but you can enable it on the console after you create your user configuration.

Single Sign-on logs events for features such as Hot Desktop, smart cards, licensing, and the Single Sign-on Service. The event log captures and verifies security-related events that you may need to track for regulatory compliance, such as for the Federal Information Processing Standard (FIPS) or for the Health Insurance Portability and Accountability Act of 1996 (HIPAA). Single Sign-on’s event log capabilities also help increase your IT security.

If you are using Single Sign-on in a XenApp environment, the event log identifies both user and session information. All logon attempt failures are captured.

To enable information event logging:
  1. In the console, find your user configuration and, from the Action menu, click Edit user configuration.
  2. In the properties of the user configuration, select Client-Side Interaction.
  3. Click Log Single Sign-on Plug-in events using Windows event logging.

The following table contains some of the standard events that Single Sign-on logs:

Standard Event Types
Logon attempt failure (plug-in software authentication)
  Logged during unsuccessful user authentication to Single Sign-on. Failure to open the credential store.
Logon attempt success (plug-in software authentication)
  Logged during successful user authentication and success opening the central store.
Logon attempt (submitting credentials)
  Logged during attempts to submit credentials to an external application.
Operations with credentials
  Logged during operations involving passwords, such as change, reveal, and identity verification.
Synchronization failures (communication)
  Logged during failure to synchronize with the central store due to communication issues.
Synchronization failures (permissions)
  Logged during failure to synchronize with the central store due to incorrect user credentials.
Smart card DataProtect encrypt/decrypt failure
  Logged during general failure associated with encrypting or decrypting smart card data.
Smart card DataProtect encrypt/decrypt failure (missing card)
  Logged when smart card is not available.
Plug-in software start up and shut down
  Logged when smart card is not available.
Missing or corrupted .dll files
  Logged when a .dll cannot be loaded correctly.

The following table contains some of the Hot Desktop events that Single Sign-on logs.

Hot Desktop Event Types
Hot Desktop session logon failure
  Logged only when there is a fatal error at session start up.
Hot Desktop session logon success
  Logged when Hot Desktop starts a session due to successful user authentication.
Hot Desktop session logoff failure
  Logged only when there is a fatal error during session termination.
Hot Desktop logoff success
  Logged when a session terminates successfully due to user input or session time-out.