5 ms·
Basically all cloud authentication services. Try signing into a bunch of apps and then signing out - with third party cookies disabled, you'll find you're still
by will4274 7y ago
Basically all cloud authentication services. Try signing into a bunch of apps and then signing out - with third party cookies disabled, you'll find you're still signed in to most of the apps, because the browser refused the (third party) session cookie clear.
- jeroenhd 7y agoThis depends on the service. I believe many authentication services actually use cross-tab communication (so they open a tab/window and can exchange messages as long as both are open). AFAIK Google makes use of that method and other one-click providers do too. That is, however, more difficult than just setting third-party cookies so smaller authentication services might choose not to use such functionality. If Chrome or Edge follows in this path though, websites won't have a choice but to make things work with this feature enabled.
- will4274 7y agoOpenID Connect implementations use iframes for logout, because that's what the spec says. Iframes are a third party context. The big Identity companies (Ping, Oracle, Microsoft) wrote the OpenID Connect spec. Google may be the odd man out (they are notorious for implementing logout poorly in general) but the biggest enterprise authentication services use iframes for logout. There is a compromise here which works for logout which was commonly implemented for a few years - supporting third party cookie clear but not set. But Apple ended this norm.