# SSO broken after rebuild with stable v3.3.3

**URL:** <https://meta.discourse.org/t/sso-broken-after-rebuild-with-stable-v3-3-3/343847>\
**Category:** SSO\
**Created:** [December 21, 2024, 10:10pm UTC](https://meta.discourse.org/t/sso-broken-after-rebuild-with-stable-v3-3-3/343847 "2024-12-21T22:10:25Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)\
**Post date:** [December 22, 2024, 1:02pm UTC](https://meta.discourse.org/t/sso-broken-after-rebuild-with-stable-v3-3-3/343847/10 "2024-12-22T13:02:23Z")

</div>

I suspect the issue here is not the [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) security fix but rather the nginx change. On `tests-passed` we had to make a followup on Thursday because it was causing problems on some environments and [another user](https://github.com/discourse/discourse/pull/30383#issuecomment-2557996967) on Github noted CSRF issues.

I have a backport ready for that: [FIX: Simplify nginx config change (#30383) by pmusaraj · Pull Request #30410 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/30410), it should be merged shortly (once someone in the team approves it, though it’s Sunday for most people). You’re welcome to give that branch a try with your SSO set up @mentalstring

---

_[View the full topic](https://meta.discourse.org/t/sso-broken-after-rebuild-with-stable-v3-3-3/343847)._
