BriskBard, CEF4Delphi, WebView4Delphi, WebUI4Delphi and WebUI4CSharp

Posted: **Thu May 16, 2019 10:27 am**

The CEF project maintainer posted a deprecation schedule and some more information.
https://magpcss.org/ceforum/viewtopic.php?f=10&t=16764

Hi All,

Google will begin blocking sign-in from CEF-based embedded web views (announced here[1] and initially discussed here[2]) on the following proposed schedule:

June 2019: block all obvious automation.

Aug 2019: block all new app from signing in using CEF.

Jan 2020: block existing app from signing in using CEF.

Google has requested feedback on this schedule. You can post your feedback here[3], or reach out to Jonathan Skelker directly.

What apps will be impacted?

This will impact any apps that sign in to Google services directly instead of using the recommended OAuth flow. Google has a resource here that can help with OAuth authentication using the system browser.

What apps will not be impacted?

This should not impact apps that are themselves genuine system browser apps (e.g. apps that are intended to replace the default system browser). If you are the author of a system browser app and have upfront concerns please reach out to Jonathan Skelker directly.

[1] https://security.googleblog.com/2019/04 ... +Blog)&m=1
[2] https://groups.google.com/a/chromium.or ... j1v_cqBgAJ
[3] http://www.appauth.io/

Posted: **Fri May 17, 2019 1:23 am**

"June 2019: block all obvious automation."

I wonder how will they assume an app is an 'obvious automation'...

Posted: **Fri Jun 14, 2019 5:42 pm**

Any news about this ? Does someone had this problem ?

Posted: **Sun Jul 28, 2019 6:09 pm**

I'm not sure I got it straight...
I can normally log in to my Google account, right now, from a self-made CEF application without any problems at all.
Wasn't that login attempt supposed to fail?

Posted: **Sun Jul 28, 2019 6:36 pm**

Google is not sharing any new information about this and they will not tell how are they going to detect that a browser is embedded or the real Chromium browser.

According to the schedule, they will only block new applications in August. Existing applications will be able to login until January 2020.

Posted: **Sun Jul 28, 2019 8:15 pm**

salvadordf wrote: ↑Sun Jul 28, 2019 6:36 pm Google is not sharing any new information about this and they will not tell how are they going to detect that a browser is embedded or the real Chromium browser.
According to the schedule, they will only block new applications in August. Existing applications will be able to login until January 2020.

Thanks for the update, Salvador!
Fortunately, Google login is not a must for my current needs but, for my future works, I'm a bit concerned about this issue.
Let's see what they will do in the next year. I hope they change their minds and let us log in as usually, i.e., in peace. \\:^]

BriskBard, CEF4Delphi, WebView4Delphi, WebUI4Delphi and WebUI4CSharp

Google will block sign-ins from CEF browsers in June 2019

Re: Google will block sign-ins from CEF browsers in June 2019

Re: Google will block sign-ins from CEF browsers in June 2019

Re: Google will block sign-ins from CEF browsers in June 2019

Re: Google will block sign-ins from CEF browsers in June 2019

Re: Google will block sign-ins from CEF browsers in June 2019

Re: Google will block sign-ins from CEF browsers in June 2019