![]() The following steps explain how to disable the allowlist: To test your application, add a specific HTTP header and value to disable the allowlist. To verify whether you'll be affected by the change, test your application for compatibility. If you're a developer that currently uses CEF for sign-in, be aware that support for this type of authentication ends on January 4, 2021. We do not allow sign-in from browsers based on frameworks like CEF or Embedded Internet Explorer. This includes scripts that automate keystrokes or clicks, especially to perform automatic sign-ins. The browser must not provide automation features. The browser must not use another browser's User-Agent string, such as Chrome or Firefox on that host. ![]() The browser must identify itself clearly in the User-Agent when connecting to. You must confirm that your browser does not contain any of the following: The browser must have a reasonably complete implementation of web standards and browser features. Your browser must not do any of the following: The browser must not proxy or alter the network communication. For more details, see our previous blog post. The browser must have JavaScript enabled. Modern browsers with security updates will continue to be supported. Alternatively, you can use a compatible full native browser for sign-in.įor limited-input device applications, such as applications that do not have access to a browser or have limited input capabilities, use limited-input device 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |