From d7dbb63d78cdd84c807ec2892e6d18cfbc25795d Mon Sep 17 00:00:00 2001
From: Timshel <Timshel@users.noreply.github.com>
Date: Mon, 18 Aug 2025 16:07:47 +0000
Subject: [PATCH] Revert
 febb0d88b30c84008bc9cd206dd916703ddde52f...80c3c91f108e002a9aa97bfe1b373dea37dc4c55
 on Enabling SSO support using OpenId Connect

---
 Enabling-SSO-support-using-OpenId-Connect.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/Enabling-SSO-support-using-OpenId-Connect.md b/Enabling-SSO-support-using-OpenId-Connect.md
index dd436b3..bc50712 100644
--- a/Enabling-SSO-support-using-OpenId-Connect.md
+++ b/Enabling-SSO-support-using-OpenId-Connect.md
@@ -145,8 +145,6 @@ 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 it will include a double `/`: `https://${domain}/application/o/${application_name}//.well-known/openid-configuration`. This can cause issues with some proxy.
-
 ## Casdoor
 
 Since version [v1.639.0](https://github.com/casdoor/casdoor/releases/tag/v1.639.0) should work (Tested with version [v1.686.0](https://github.com/casdoor/casdoor/releases/tag/v1.686.0)).