>What happened to sending my login info over an HTTPS connection in the background and getting a session token back? I guess that's too simple for Google.
Not exposing an HTTP endpoint that easily lets you check if a Google account with said credentials exists (because it has to work from anywhere) and not maintaining an API that supports all the weird edge cases to logging in to Google (2FA, showing notices, locked out accounts, requiring additional authentication).
You essentially want this mess with application specific passwords back?
>What happened to sending my login info over an HTTPS connection in the background and getting a session token back? I guess that's too simple for Google.
Not exposing an HTTP endpoint that easily lets you check if a Google account with said credentials exists (because it has to work from anywhere) and not maintaining an API that supports all the weird edge cases to logging in to Google (2FA, showing notices, locked out accounts, requiring additional authentication).
You essentially want this mess with application specific passwords back?