Yubikey is not getting detected by the webview2 web browser control

Resolved Yubikey is not getting detected by the webview2 web browser control

How-to

Votes

Undo

Shuchi Aggarwal
PowerBuilder
Wednesday, 13 March 2024 09:38 AM UTC

Hi,

We are trying to integrate our application which is build in Powerbuilder with Azure AD for user authentication.

Currently our application is using PB 2019 R3 (build 2703). Based on appeon suggestions, we tried upgrading powerbuilder to PB 2019 R3 (build 2803), as well as PB 2022 R3.

We are opening the Azure authorize URL in the web browser control which is provided by powerbuilder and as per documentation, it is using webview2 web browser control.

We are facing the issue that 5C Yubikey is not getting detected on the webview2 web browser control which is being opened inside our application.

Also, when we are trying to trigger the same URL in a local web browser control (chrome or msedge), the yubikey is getting detected.

Please note that our application is being run on a citrix workspace.

Has anyone tried using the webview2 web browser control? Has anyone faced this issue earlier?

Please share suggestions/path forward for this issue.

Responses (3)

Rian Howler Accepted Answer Pending Moderation

Saturday, 17 August 2024 00:36 AM UTC
PowerBuilder
# 1

Hello, did you ever happen to find a solution for this issue? I'm seeing the exact same problem when running from a Citrix machine. The Yubikey is recognized and prompts for a pin when tested in a browser (edge or chrome) on the same system, however when launching the app using the webveiw2 component it's not seeing the Yubikey. We're using Entra authentication as well. Both test are done via Citrix, so it's only the webview2 control that seems to have the problem.

Thanks in advance!

Comment

Rian Howler
Thursday, 22 August 2024 02:14 AM UTC

In case anyone runs into this problem - I found the fix.

https://docs.citrix.com/de-de/citrix-virtual-apps-desktops/secure/fido2.html

Near the bottom of the article it details additional registry keys required to pass through FIDO2 keys to the msedgewebvew2.exe process in a Citrix session.

Hope this helps anyone in the future.

Helpful 0

Chris Pollach @Appeon
Thursday, 22 August 2024 02:22 AM UTC

Hi Rian;

Thank you for sharing the resolution to allow Citrix to accept the WebView2 processing!

Regards ... Chris

Helpful 0

There are no comments made yet.

Shuchi Aggarwal Accepted Answer Pending Moderation

Thursday, 14 March 2024 05:39 AM UTC
PowerBuilder
# 2

Hi,

PB 2019 R3 (Build 2797) uses Webview2.

PSB from appeon website:

The following new features or enhancements are added to PowerBuilder 2019 R3 MR 2797:

The PowerBuilder WebBrowser control has upgraded the underlying web platform from Chromium Embedded Framework (CEF) to Microsoft Edge WebView2.

Also, we tried with PB 2022 R3 as well.

Below is the test case:

1. Create a PB application

2. using the Webbrowser control, we are trying to open Azure authorize URL.

3. It opens webview2 web browser with Azure (Entra) authorize URL, asks for Entra ID to be entered, but then the yubikey is not getting detected.

PFA the screenshot.

We raised a support ticket as well, but it did not help much. They suggested to post the question on community.

When we open msedge or chrome webbrowser locally on the machine, the yubikey gets detected, but its not getting detected by the web browser control (webview2) which is opened inside the PB application.

Comment

Load more comments

Andreas Mykonios
Thursday, 14 March 2024 13:37 PM UTC

What I was saying and was not really clear, is that there may be a limitation in the way webview2 is "wrapped" to webviewer control in powerbuilder.

Andreas.

Helpful 0

Chris Pollach @Appeon
Thursday, 14 March 2024 17:17 PM UTC

Hi Shuchi;

This sounds like a possible Citrix configuration, Proxy server, Firewall, or Antivirus issue in the Citrix environment maybe?

Regards ... Chris

Helpful 1

David Peace (Powersoft)
Wednesday, 21 August 2024 16:02 PM UTC

I'm thinking that this would be a security constraint in the Citrix environment. Perhaps the WebView2 in PB is not recognized as a safe browser or something?

Helpful 0

There are no comments made yet.

Armeen Mazda @Appeon Accepted Answer Pending Moderation

Wednesday, 13 March 2024 13:55 PM UTC
PowerBuilder
# 3

I'm confused by your comment about WebView2 when you say you are on PB 2019 R3. PB 2019 R3 does not use WebView2. PowerBuilder 2022 R2 and newer supports WebView2. https://docs.appeon.com/pb/whats_new/WebBrowser_engine_upgrade.html

Do you have same problem with both PB 2019 R3 and PB 2022 R3?

Can you provide a test case? If yes, please open a support ticket.

Comment

Arnd Schmidt
Thursday, 14 March 2024 13:00 PM UTC

It is really confusing that an appeon offical claims that PB 2019 R3 does not use WebView2. Eventually "use" means something different.

https://docs.appeon.com/pb/release_bulletin_for_pb/Build-2797-MR-Improvements.html

Helpful 0

Andreas Mykonios
Thursday, 14 March 2024 13:06 PM UTC

You are right. WebView2 was also introduced to PB 2019 R3 (2797).

Andreas.

Helpful 0

Armeen Mazda @Appeon
Thursday, 14 March 2024 17:03 PM UTC

You are correct Arnd... it is confusing, and I forgot that we switched out the engine in the later build of 2019 R3. We did this for security reasons so that customers on this long-term support version of 2019 R3 have an "evergreen" option to keep their web browser engine always up to date.

Helpful 1

There are no comments made yet.

Page :
1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.

Please login to post a reply

You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »

Forgot Password?

We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.