# SSO-Anmeldung scheint nicht mehr zu funktionieren

**URL:** <https://meta.discourse.org/t/sso-login-appears-to-have-stopped-working/215691>\
**Category:** Bug\
**Created:** [23. Januar 2022 um 12:13 UTC](https://meta.discourse.org/t/sso-login-appears-to-have-stopped-working/215691 "2022-01-23T12:13:12Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [23. Januar 2022 um 14:54 UTC](https://meta.discourse.org/t/sso-login-appears-to-have-stopped-working/215691/6 "2022-01-23T14:54:32Z")

</div>

Für den stabilen Zweig ist dies die Korrektur:

> <https://github.com/discourse/discourse/commit/909de9b36c86d98793127fadc54bc3e656949c1e>
>
> This is a workaround a behavior change in Chromium v97.
> The following text was …sent to the blink-dev mailing list:
> 
> \> This change broke a SingleSignOn login on the FOSS software Discourse. We have a flow like:
> \>
> \> 1. User visits forum.siteA.com, click login
> \> 2. Gets redirected to idp.siteB.com
> \> 3. Fills login details
> \> 4. Gets redirected to forum.siteA.com/session/sso\_login?parameters
> \> 5. Gets redirected to forum.siteA.com/homepage
> \>
> \> On step 4, the response includes a \`set-cookie\` header, with proper \`HttpOnly; SameSite=Lax; Secure \`and set. But if there is an active service worker, the login will fail as that cookie will be rejected by Chromium due to SameSite rules now.
> \>
> \> t=2971 \[st=258\] COOKIE\_INCLUSION\_STATUS
> \> --\> domain = "forum.siteA.com"
> \> --\> name = "\_t"
> \> --\> operation = "store"
> \> --\> path = "/"
> \> --\> status = "EXCLUDE\_SAMESITE\_LAX, DO\_NOT\_WARN"
> \>
> \> The service worker is a vanilla WorkboxJS service worker that intercepts all GETs with the "Network First" strategy.
> \>
> \> Disabling the service worker or using Firefox results in a successful login. There is no warning in either DevTools network tab nor the console that the cookie was rejected.
> \>
> \> Chrome 96: login works
> \> Chrome 97: login does not work
> \> Chrome 98: login does not work
> \>
> \> Is this expected behavior? Even if the request \`GET forum.siteA.com\` was initiated because of a redirect from a different domain, is it expected that Chrome will silently drop same site cookies from forum.siteA.com?
> 
> Co-authored-by: Rafael dos Santos Silva \<xfalcox@gmail.com\>

Es gibt einen ähnlichen Commit auf Beta und Tests-bestanden.

---

_[View the full topic](https://meta.discourse.org/t/sso-login-appears-to-have-stopped-working/215691)._