It turns out that we could not 100% scrape gaia_auth. Its success.html is used as the landing page for successful sign-in. I would keep that and remove all other files.
The files in chromeos-assets are obsolete. We already have all gaia_auth bunlded as a component extension. My comment in #2 is that we could not get rid of the component extension fully because its success.html is still used as a landing page. If we want to get rid of that, we need to figure out a replacement landing page and might need to coordinate some server side page too.
Re #7: If Gaia takes the continue URL from "continue" param only and there is no hard coded URL like the following:
chrome-extension://mfffpogegjflfpflabcdkioaeobkgjik/success.html
then we just need to figure out a new landing URL to get rid of the extension completely.
+omrilio
Is there a historical or technical reason for the success page? Could we not just take the user directly to the next step in new user flow upon successful login?
In old days, this url is used as a signal of auth success. But I don't think it is needed in new code now as we use http headers and oauth code cookie to indicate the auth success. Not sure whether it is still needed for Gaia code though because server side might need to do a redirect somewhere after the auth.
Comment 1 by bugdroid1@chromium.org
, Feb 7 2017