Re: [OAUTH-WG] Full Third-Party Cookie Blocking

2020-03-25 Thread David Waite
More specifically, SSO will not work anymore without either: - prompting the user (via Storage Access API) - using explicit front-channel mechanisms (popups and redirects) - using back-channel mechanisms (refresh tokens and some backchannel logout infrastructure) (FWIW, I proposed a back-channel

Re: [OAUTH-WG] Full Third-Party Cookie Blocking

2020-03-25 Thread Torsten Lodderstedt
> On 25. Mar 2020, at 14:55, Dominick Baier wrote: > > This > > https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/ > > Really means that “modern” SPAs based on a combination of OIDC and OAuth will > not work anymore > > both > > * silent-renew for access token

[OAUTH-WG] Full Third-Party Cookie Blocking

2020-03-25 Thread Dominick Baier
This https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/ Really means that “modern” SPAs based on a combination of OIDC and OAuth will not work anymore both * silent-renew for access token management * OIDC JS session notifications Will not work anymore. Or don’t work