Olivier 'reivilibre 6c7e05fe20 Allow Synapse to start up even when discovery fails for an OpenID Connect provider. (#19509) ...

Fixes: #8088

Previously we would perform OIDC discovery on startup,
which involves making HTTP requests to the identity provider(s).

If that took a long time, we would block startup.

If that failed, we would crash startup.

This commit:

- makes the loading happen in the background on startup
- makes an error in the 'preload' non-fatal (though it logs at CRITICAL
for visibility)
- adds a templated error page to show on failed redirects (for
unavailable providers), as otherwise you get a JSON response in your
navigator.
- This involves introducing 2 new exception types to mark other
exceptions and keep the error handling fine-grained.

The machinery was already there to load-on-demand the discovery config,
so when the identity provider
comes back up, the discovery is reattempted and login can succeed.

Signed-off-by: Olivier 'reivilibre <oliverw@matrix.org>

2026-03-24 17:39:21 +00:00

..

internal/dockerutil

Allow Synapse to start up even when discovery fails for an OpenID Connect provider. (#19509)

2026-03-24 17:39:21 +00:00

federation_test.go

Add in-repo Complement tests (#19406)

2026-02-05 17:11:55 -06:00

main_test.go

Add in-repo Complement tests (#19406)

2026-02-05 17:11:55 -06:00

oidc_test.go

Allow Synapse to start up even when discovery fails for an OpenID Connect provider. (#19509)

2026-03-24 17:39:21 +00:00

synapse_version_check_test.go

Add in-repo Complement test to sanity check Synapse version matches git checkout (#19476)

2026-03-11 15:30:32 -05:00