3 ms·
No, it's still easy to perform oauth2 login. User clicks log in at p1.com, they get forwarded to a1.com which checks their (now first-party) cookies, then once
by michaelt 6y ago
No, it's still easy to perform oauth2 login.
User clicks log in at p1.com, they get forwarded to a1.com which checks their (now first-party) cookies, then once they're logged in they get forwarded back to p1.com with a token in an URL parameter.
- sudhirj 6y agoAh, right, thanks. So this is a problem only if we have in-page widgets from a1.com that load on p1.com and hope to find a the currently logged in user there. Makes sense, that's basically what an ad is.
- kevin_thibedeau 6y agoThis weakens security. Now auth tokens can be logged or actively intercepted on corporate networks with TLS MITM and these URLs will eventually find their way into emails and other unencrypted locations. Not exactly progress.
- SilverRed 6y agoIf you have TLS MITM malware on your computer than security is already dead.
- michaelt 6y agoThe behaviour with third party cookies blocked is how oauth2 works by design. Even without third party cookie blocking, if you're at p1.com and you click to log in with a1.com but you're not logged into a1.com yet, you get forwarded to a1.com to sign in. So with third party cookies blocked, it's no less secure than it was before.