Skip to main content
Skip table of contents

Troubleshoot authentication process on VDAs receiving login information from Veridium fasless component

Please follow the steps below to capture relevant events when a Citrix session is launched using Veridium authentication on VDAs:

  1. Open Event Viewer

  2. Select Windows Logs / Application.

  3. Filter Event Logs for the following Event Sources

    1. Citrix Desktop Services

    2. Citrix Profile Management

    3. Veridium-BopsHDX

      image-20250723-142912.png

 Below is the event flow triggered during session startup via Citrix Workspace:

  1. Veridium SSO

    Component: VeridiumBops-HDX

        Event ID: 100

            Logs the user certificate request via VeridiumRA. Duration (in ms) is included in the message. If the duration is high, we may need to further corelate with the Event logs from VeridiumRA.

image-20250723-142931.png
  1. Windows Logon Begins

    After the certificate is retrieved, a logon package is prepared. From this point further, Veridium components are no longer involved.

  2. Citrix Session Preparation

    Component: Citrix Desktop Services

    Event ID: 1027

    Indicates Windows logon was successful and the Citrix user session is being prepared.

    image-20250723-142953.png
  3. Session Launch Confirmation

    Component: Citrix Profile Management

    Event ID: 1000

    Description: Confirms that the application/session has launched on the end user's device.

    image-20250723-143007.png

Collecting Events from VeridiumRA machines (only if the duration in VeridiumBops-HDX Event ID 100 message is high)

  1. Open Event Viewer.

  2. Fiter Event logs for VeridiumRA event source and Event ID 200.

  3. Verify duration in the message and if the certificate was requested in the PKI or was retrieved from cache.

    1. In the event message there is a TimeProfile that provides duration for all operations.  

image-20250723-143020.png

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.