• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Yubikey is not getting detected by the webview2 web browser control

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

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

  1. How-to
0
Votes
Undo
  1. Shuchi Aggarwal
    Shuchi Aggarwal
  2. PowerBuilder
  3. 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.

 

Converting SOAP to REST in PB2022
QRcode Generator
Responses (2)
Shuchi Aggarwal
Shuchi Aggarwal Accepted Answer Pending Moderation
  1. Thursday, 14 March 2024 05:39 AM UTC
  2. PowerBuilder
  3. # 1

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.

Attachments (1)
Not detecting the yubikey.jpg Not detecting the yubikey.jpg
Comment
Load more comments
Shuchi Aggarwal
  1. Shuchi Aggarwal
  2. Thursday, 14 March 2024 13:26 PM UTC
This is not true. When I run this application on my local laptop, then webview2 web browser is detecting the yubikey. When when we are running this application on a citrix machine, then webview2 web browser is detecting the yubikey. Whereas msedge or chrome browser on the same citrix machine is detecting the yubikey.
  1. Helpful
Andreas Mykonios
  1. Andreas Mykonios
  2. 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.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. 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
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 March 2024 13:55 PM UTC
  2. PowerBuilder
  3. # 2

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
  1. Arnd Schmidt
  2. 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
  1. Helpful
Andreas Mykonios
  1. Andreas Mykonios
  2. Thursday, 14 March 2024 13:06 PM UTC
You are right. WebView2 was also introduced to PB 2019 R3 (2797).

Andreas.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. 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.
  1. 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.