1. Prabal awasthi
  2. PowerBuilder
  3. Monday, 5 July 2021 06:51 AM UTC

I am Using Microsoft Web Browser OLE in PowerBuilder 2017 R3, I am using this Web Browser to take credentials from user and generating the OAuth2.0 Authorization Code for further use to generate access token, but when i give the UserId and click on next , Google sign in screen showing -

"Couldn't sign you in
This browser or app may not be secure.
Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in."

Is there any way to avoid this problem , i am stuck here for a week. 

Thanks

Attachments (1)
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 5 July 2021 17:19 PM UTC
  2. PowerBuilder
  3. # 1

Import this into you registry and try again: see attachment.

Attachments (1)
Comment
  1. Prabal awasthi
  2. Tuesday, 6 July 2021 07:18 AM UTC
Yes Miguel Leeuwe ,

In PB 2019 its working, but our application currently running in PB2017 R3. Is there any other way to solve this issue in

PB2017.

Thanks
  1. Helpful
  1. Miguel Leeuwe
  2. Tuesday, 6 July 2021 07:28 AM UTC
If all the suggestions made by others don't work, then maybe you could try to implement another ActiveX control: There's C# CEF browsers out there, but that's a bit tedious, since you'll have to wrap that code up in an activex to be able to place it on your window. It will also force your application to be 32bit.

For a example, have a look at https://github.com/cefsharp/CefSharp , maybe you're lucky and they've already wrapped it up for ActiveX, as there seems to be a "winforms" branch. (haven't tried myself).

Good luck!
  1. Helpful
  1. Miguel Leeuwe
  2. Tuesday, 6 July 2021 07:42 AM UTC
here's the official link: https://github.com/cefsharp/CefSharp

  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 5 July 2021 16:16 PM UTC
  2. PowerBuilder
  3. # 2

Hi Prabal, 

You need to upgrade to PowerBuilder 2019 R3 and use the new Chromium Web Browser control.  The old Web Browser control is Internet Explorer and has too many limitations .  For example, the new Chromium Web Browser control supports HTML5, HTTP/2, etc. very well. Also, the new Chromium Web Browser control supports doing OAuth2.0 authorization so that's one of the reasons why we supported many JavaScript functions in this new control.

Best regards,
Armeen

Comment
There are no comments made yet.
René Ullrich Accepted Answer Pending Moderation
  1. Monday, 5 July 2021 12:25 PM UTC
  2. PowerBuilder
  3. # 3

I think it's because MS WebBrowser OLE runs in a compatibility mode by default.

Try to change the compatibility mode in the registry (FEATURE_BROWSER_EMULATION) or use X-UA-Compatible meta tag (e.g. IE=edge) in your HTML.

Comment
There are no comments made yet.
Benjamin Gaesslein Accepted Answer Pending Moderation
  1. Monday, 5 July 2021 11:44 AM UTC
  2. PowerBuilder
  3. # 4

Hi,

as far as I know the old web browser control does not support Javascript, which might be the issue as Google requires JS to be active in order to sign in. Or the OLE browser might not be recognized as a valid browser, I'm not entirely sure. PB 2019R3 has a Chromium based native web browser control which might work but no guarantees.

Comment
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.