PSM ConnectionManager FIDO2 Usage Within a Citrix VDI Session

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PSM ConnectionManager FIDO2 Usage Within a Citrix VDI Session

L1 Bithead

My organization requires a FIDO2 security key to be used when logging into CyberArk. The WebView2 based browser that PSM ConnectionManager uses when logging in works with FIDO2 / WebAuthn in almost all scenarios other than within a Citrix VDI session. Citrix themselves does provide documentation on how to setup FIDO2 redirections for msedgewebview2.exe based applications (https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/secure/fido2.html#advanced-configuration-...). These instructions are pretty straightforward other than the first registry key edit that asks to “add full path of the msedgewebview2.exe here”:

Field_Content_versions_oct20__068Vy00000gGc7gIAC.png 

 

While I could add the registry key for the current version of msedgewebview2.exe, every time Microsoft Edge gets an update, WebView2 also gets an update which changes the full path to msedgewebview2.exe. If I add the full path for the current version of msedgewebview2.exe (version 138) and Microsoft releases Edge 139 tomorrow, the registry key would no longer be valid which in turn, breaks logging into the PSM ConnectionManager app.

 

I have found a kludgy solution for this issue by setting the WEBVIEW2_BROWSER_EXECUTABLE_FOLDER environment variable to point at a fixed version of the WebView2 Runtime that I manually installed. While this works, this change forces ALL applications that use WebView2 to use the fixed version, effectively stopping all WebView2 updates on the machine with the environment variable. Although this technically works, I would ideally like to use the WebView2 runtime that gets automatically updated alongside Edge.

 

Does anyone know of an alternative way to specify what version of msedgewebview2.exe the PSM ConnectionManager uses? Alternatively, has anyone else gotten the PSM ConnectionManager working with FIDO2 within Citrix CVAD sessions?

2 REPLIES 2

L7 Applicator

Hi @Alexander Swinford​ 

 

You are right, in the Citrix VDI where correct path is often required for redirection. Also, another problem is that the msedgewebview2.exe executable resides in a version specific folder within the Microsoft Edge installation path and hence upgrade will change it.

 

Please raise a Support case with CybeArk team and confirm with them if they have any specific recommendations or known solutions for FIDO2 authentication with PSM ConnectionManager in Citrix VDI, considering the dynamic WebView2 path. They might have internal documentation.

 

Also please check with the Citrix whether wildcards be used in the path C:\Program Files (x86)\Microsoft\Edge\Application\*\msedgewebview2.exe or are there any alternative methods in Citrix to manage WebView2 FIDO2 redirection without hardcoding the version specific path ?

 

Hope it helps !

L4 Transporter

using the webauthn webhook can be very fiddly indeed in my experience.

 

Is it possible to enable USB passthrough to the Citrix session? This can be configured to restrict the USB device types, to mitigate any risk of allowing users to attach USB storage.

  • 322 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!