From 80c3c91f108e002a9aa97bfe1b373dea37dc4c55 Mon Sep 17 00:00:00 2001 From: Timshel Date: Mon, 18 Aug 2025 15:49:25 +0000 Subject: [PATCH] Revert, it's not by spec :( cf https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfigurationRequest --- Enabling-SSO-support-using-OpenId-Connect.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Enabling-SSO-support-using-OpenId-Connect.md b/Enabling-SSO-support-using-OpenId-Connect.md index 10092f1..dd436b3 100644 --- a/Enabling-SSO-support-using-OpenId-Connect.md +++ b/Enabling-SSO-support-using-OpenId-Connect.md @@ -145,7 +145,7 @@ Server configuration should look like: - `SSO_CLIENT_ID` - `SSO_CLIENT_SECRET` -:warning: The trailing `/` of the `SSO_AUTHORITY` means that when building the full URL for the configuration endpoint (as defined in the [spec](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig)), it will include a double `/`: `https://${domain}/application/o/${application_name}//.well-known/openid-configuration`. This can cause issues with some proxy. +:warning: The trailing `/` of the `SSO_AUTHORITY` means that when building the full URL for the configuration endpoint it will include a double `/`: `https://${domain}/application/o/${application_name}//.well-known/openid-configuration`. This can cause issues with some proxy. ## Casdoor