• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • New WebBrowser Control and Google authenticate error

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

Resolved New WebBrowser Control and Google authenticate error

  1. Issue
0
Votes
Undo
  1. Thierry Garrigues
    Thierry Garrigues
  2. PowerBuilder
  3. Tuesday, 4 May 2021 07:45 AM UTC

Hi

With our application we can synchronize with the Google calendar.

To authenticate with Google, we use OLE Control Internet Explorer. It work fine.

After migration in PowerBuilder 2019 R3, I try to use the new web control provided in PowerBuilder but it doesn't work.

Google seems not to recognize the web browser and is blocking authentication with this error :

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

Does anyone have a solution for this problem?

Regards

Thierry

Attachments (1)
Web Browser error with Google.png Web Browser error with Google.png
Datawindow save as
Saving multiple DataWindows to one PDF file
Responses (2)
ritesh desai
ritesh desai Accepted Answer Pending Moderation
  1. Thursday, 6 May 2021 08:16 AM UTC
  2. PowerBuilder
  3. # 1

Pl. post how to resolved this problem.

Regards

Comment
Load more comments
ritesh desai
  1. ritesh desai
  2. Friday, 7 May 2021 04:07 AM UTC
thanks , but its not work for me
  1. Helpful
ritesh desai
  1. ritesh desai
  2. Friday, 7 May 2021 06:44 AM UTC
It's work fine in both PB IDE and exe, after changing the UserAgent settings and restarted PB IDE.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 7 May 2021 14:37 PM UTC
Awesome Ritesh .. thanks for letting us know! :-)
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 4 May 2021 08:40 AM UTC
  2. PowerBuilder
  3. # 2

Please provide test case and open a support ticket.

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 5 July 2021 21:29 PM UTC
Hi Prabal;

Sounds like this might be worth opening a Support Ticket and attaching a small Test Case PB App to the ticket for Appeon to look into this issue deeper for you.

Regards ... Chris
  1. Helpful
S Lambert
  1. S Lambert
  2. Monday, 18 July 2022 13:59 PM UTC
Hello,



I also have this problem, using PB2021 Build 1288. Have not tested it yet with WebBrowserSet("UserAgent", "AppeonWebBrowser"). But I'm curious if it is

solved by default in PB.



Regards, Steven
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 20 July 2022 17:08 PM UTC
Hi Steven, There is nothing for PB to solve. This is Google's own policy of not allowing embedded Web browsers to do OAuth requests. Setting the UserAgent to AppeonWebBrowser is workaround to bypass Google's check. We are not going to default the workaround as that may cause problems with most other Websites. So this is just something as developer you will need to do.
  1. Helpful
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.