Please disable your adblock and script blockers to view this page

Guidance to developers affected by our effort to block less secure browsers and applications


Google
Chromium Embedded Framework - CEF
MITM
OAuth
JavaScript
HTTPS
Replay

Chrome
Firefox
Embedded Internet Explorer
ModHeader
Post


Lillan Marie Agerup


hdrMap.insert(std::make_pair("Google-Accounts
ModHeader


Modern


Node.js

No matching tags



Chrome

No matching tags

Positivity     27.00%   
   Negativity   73.00%
The New York Times
SOURCE: https://developers.googleblog.com/2020/08/guidance-for-our-effort-to-block-less-secure-browser-and-apps.html
Write a review: Hacker News
Summary

How to enable sign-in on your embedded framework-based apps using browser-based OAuth 2.0 flows. If you're an app developer and use CEF or other clients for authorization on devices, use browser-based OAuth 2.0 flows. Browsers Your browser must not do any of the following: We do not allow sign-in from browsers based on frameworks like CEF or Embedded Internet Explorer. Add Google-Accounts-Check-OAuth-Login:true to your HTTP request headers. How to enable sign-in on your embedded framework-based apps using browser-based OAuth 2.0 flows. If you're an app developer and use CEF or other clients for authorization on devices, use browser-based OAuth 2.0 flows. Browsers Your browser must not do any of the following: We do not allow sign-in from browsers based on frameworks like CEF or Embedded Internet Explorer. Add Google-Accounts-Check-OAuth-Login:true to your HTTP request headers. If you're an app developer and use CEF or other clients for authorization on devices, use browser-based OAuth 2.0 flows. Your browser must not do any of the following:

As said here by Google