Update RP-Initiated Logout target URLs.

The URLs we're using are not actually pointing to the OIDC RP-Initiated Logout Specs. Fixes: gh-12081
spring-projects · Oct 28, 2022 · 9f398d8 · 9f398d8
1 parent a2bff26
commit 9f398d8
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/docs/modules/ROOT/pages/reactive/oauth2/login/advanced.adoc b/docs/modules/ROOT/pages/reactive/oauth2/login/advanced.adoc
@@ -645,7 +645,7 @@ If more than one `ClientRegistration` is configured for OpenID Connect 1.0 Authe
 == OpenID Connect 1.0 Logout
 
 OpenID Connect Session Management 1.0 allows the ability to log out the End-User at the Provider using the Client.
-One of the strategies available is https://openid.net/specs/openid-connect-session-1_0.html#RPLogout[RP-Initiated Logout].
+One of the strategies available is https://openid.net/specs/openid-connect-rpinitiated-1_0.html[RP-Initiated Logout].
 
 If the OpenID Provider supports both Session Management and https://openid.net/specs/openid-connect-discovery-1_0.html[Discovery], the client may obtain the `end_session_endpoint` `URL` from the OpenID Provider's https://openid.net/specs/openid-connect-session-1_0.html#OPMetadata[Discovery Metadata].
 This can be achieved by configuring the `ClientRegistration` with the `issuer-uri`, as in the following example:

diff --git a/docs/modules/ROOT/pages/servlet/oauth2/login/advanced.adoc b/docs/modules/ROOT/pages/servlet/oauth2/login/advanced.adoc
@@ -838,7 +838,7 @@ If more than one `ClientRegistration` is configured for OpenID Connect 1.0 Authe
 == OpenID Connect 1.0 Logout
 
 OpenID Connect Session Management 1.0 allows the ability to log out the End-User at the Provider using the Client.
-One of the strategies available is https://openid.net/specs/openid-connect-session-1_0.html#RPLogout[RP-Initiated Logout].
+One of the strategies available is https://openid.net/specs/openid-connect-rpinitiated-1_0.html[RP-Initiated Logout].
 
 If the OpenID Provider supports both Session Management and https://openid.net/specs/openid-connect-discovery-1_0.html[Discovery], the client may obtain the `end_session_endpoint` `URL` from the OpenID Provider's https://openid.net/specs/openid-connect-session-1_0.html#OPMetadata[Discovery Metadata].
 This can be achieved by configuring the `ClientRegistration` with the `issuer-uri`, as in the following example:

diff --git a/...ework/security/oauth2/client/oidc/web/logout/OidcClientInitiatedLogoutSuccessHandler.java b/...ework/security/oauth2/client/oidc/web/logout/OidcClientInitiatedLogoutSuccessHandler.java
@@ -41,7 +41,7 @@
  * @author Josh Cummings
  * @since 5.2
  * @see <a href=
- * "https://openid.net/specs/openid-connect-session-1_0.html#RPLogout">RP-Initiated
+ * "https://openid.net/specs/openid-connect-rpinitiated-1_0.html">RP-Initiated
  * Logout</a>
  * @see org.springframework.security.web.authentication.logout.LogoutSuccessHandler
  */

diff --git a/...y/oauth2/client/oidc/web/server/logout/OidcClientInitiatedServerLogoutSuccessHandler.java b/...y/oauth2/client/oidc/web/server/logout/OidcClientInitiatedServerLogoutSuccessHandler.java
@@ -43,7 +43,7 @@
  * @author Josh Cummings
  * @since 5.2
  * @see <a href=
- * "https://openid.net/specs/openid-connect-session-1_0.html#RPLogout">RP-Initiated
+ * "https://openid.net/specs/openid-connect-rpinitiated-1_0.html">RP-Initiated
  * Logout</a>
  * @see org.springframework.security.web.server.authentication.logout.ServerLogoutSuccessHandler
  */