Product documentation
Citrix Virtual Apps and Desktops
Current Release Service 2507 LTSR 2503 2411 2407 2402 LTSR 2311 2203 LTSR
View PDF

Troubleshooting

December 23, 2025
Contributed by: 
C

The following steps should be followed to troubleshoot FIDO2 redirection issues:

  1. Check system requirements

    1. Validate system requirements are being met for FIDO2 redirection based on the official Citrix documentation.

  2. Verify device connection

    1. For physical FIDO2 keys:

      1. Ensure the FIDO2 key is correctly inserted and visible on the client endpoint.
      2. Use your operating system device manager (e.g., Device Manager on Windows, System Information on macOS) to confirm the device is recognized and functioning.
      3. If the device is not detected:
        1. Try reinserting the key or using a different USB port.
        2. Test the key on another device to rule out hardware issues.

    2. For built-in authenticators (ex. Windows Hello, etc.) -

      1. Confirm the feature is enabled and configured on your client device.

    3. This is important because if the client device does not recognize the FIDO2 key, Citrix cannot redirect it to the HDX session.

  3. Verify Citrix policy settings and configuration

    1. Review FIDO2/WebAuthn redirection and USB redirection settings in your Citrix policies.

      1. FIDO2 redirection policy is enabled.
      2. If EdgeWebView2 or custom desktop applications are being used, appropriate file paths are added in the FIDO2 Allowed Processes policy setting.
      3. No device rules are set for FIDO2 keys to redirect the device using generic USB redirection.

    2. If Citrix components have been updated recently, verify that your configuration aligns with the new versions.

  4. Use HDX Monitor for Diagnostics

    1. Launch an HDX session and open the web browser or the UWP application and navigate to the authentication page.

    2. Select the sign in method as security key or Webauthn or FIDO2. You should see a dialog prompt from the wfica32.exe process as a result of the FIDO2 call being redirected (see attached screenshot). If this isn’t the case:

      1. Ensure that the key is not being redirected using the generic USB virtual channel. If the key is redirected inside the HDX session, you will likely see a dialog prompt that says “Insert your security key into the USB port”. To resolve this, disable USB redirection or ensure that the security key is not redirected inside the HDX session.
      2. Open HDX Monitor in the HDX session and navigate to the FIDO2 - Webauthn Redirection node.
      3. Ensure that the FIDO2 Allow Redirection policy is set to True and the application that requires FIDO2/WebAuthn authentication is listed in the FIDO2 Redirection Hooked Applications. If the application is not present, add it to the appropriate registry location based on the information in the advanced configuration.
      4. Ensure that the full path of the applications that require FIDO2/WebAuthn authentication are listed in the FIDO2 Allowed Processes Studio Policy. If the full path is not present, add it to the FIDO2 allowed processes policy setting in Studio. For additional information, reference the configurations section.
      5. (Legacy) If FIDO2 redirection is configured using the legacy based registry settings, ensure that the full path of the applications that require FIDO2/WebAuthn authentication are listed in the FIDO2 Allowed Processes registry setting. If the full path is not present, add it to the FIDO2 allowed processes policy setting in Studio. For additional information, reference the configurations section.

Note:

If you do not already have HDX Monitor installed on your session host, you can install it from the Support folder of the Citrix Virtual Apps and Desktops installer.

  1. Collect logs and contact technical support

    1. If the issue persists after following the above steps -

      1. Collect HDX Monitor output, Citrix Workspace App and VDA CDF logs.
      2. Document all troubleshooting steps you have taken and any error messages encountered.
      3. Contact your IT support team or Citrix Support, providing the collected information for faster resolution.
Troubleshooting
December 23, 2025
Contributed by: 
C
December 23, 2025
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.