Supporting the Chrome identity API will allow users to authenticate via Google into Chrome extensions. This will not affect existing workflows or user experience.
I have a Chrome extension that needs users to authenticate via Google. Since Orion version 1.3.9 blocked off 3rd party cookies, my extension users can't sign in via session cookies any more. The identify API is the preferred way to authenticate users via Google, but it's not currently supported (only placeholder in place).
