From efae2134a97bb1b4d865159c0146283086c4fd2e Mon Sep 17 00:00:00 2001
From: Hero Wanders <9137466+hwanders@users.noreply.github.com>
Date: Sat, 24 Aug 2024 01:01:57 +0200
Subject: [PATCH] fix source code block language syntax

same as in https://github.com/spring-projects/spring-security/pull/15566
included here to prevent conflicts
---
 .../ROOT/pages/reactive/oauth2/login/logout.adoc     |  8 ++++----
 .../ROOT/pages/servlet/oauth2/login/logout.adoc      | 12 ++++++------
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/modules/ROOT/pages/reactive/oauth2/login/logout.adoc b/docs/modules/ROOT/pages/reactive/oauth2/login/logout.adoc
index d3e03c10fbd..c1545aeb74f 100644
--- a/docs/modules/ROOT/pages/reactive/oauth2/login/logout.adoc
+++ b/docs/modules/ROOT/pages/reactive/oauth2/login/logout.adoc
@@ -135,7 +135,7 @@ To enable this, you can stand up the Back-Channel Logout endpoint in the DSL lik
 ======
 Java::
 +
-[source=java,role="primary"]
+[source,java,role="primary"]
 ----
 @Bean
 public SecurityWebFilterChain filterChain(ServerHttpSecurity http) throws Exception {
@@ -153,7 +153,7 @@ public SecurityWebFilterChain filterChain(ServerHttpSecurity http) throws Except
 
 Kotlin::
 +
-[source=kotlin,role="secondary"]
+[source,kotlin,role="secondary"]
 ----
 @Bean
 open fun filterChain(http: ServerHttpSecurity): SecurityWebFilterChain {
@@ -209,7 +209,7 @@ You can achieve this by configuring a custom `ReactiveOidcSessionRegistry`, like
 ======
 Java::
 +
-[source=java,role="primary"]
+[source,java,role="primary"]
 ----
 @Component
 public final class MySpringDataOidcSessionRegistry implements ReactiveOidcSessionRegistry {
@@ -238,7 +238,7 @@ public final class MySpringDataOidcSessionRegistry implements ReactiveOidcSessio
 
 Kotlin::
 +
-[source=kotlin,role="secondary"]
+[source,kotlin,role="secondary"]
 ----
 @Component
 class MySpringDataOidcSessionRegistry: ReactiveOidcSessionRegistry {
diff --git a/docs/modules/ROOT/pages/servlet/oauth2/login/logout.adoc b/docs/modules/ROOT/pages/servlet/oauth2/login/logout.adoc
index 756bff28225..32577615ed2 100644
--- a/docs/modules/ROOT/pages/servlet/oauth2/login/logout.adoc
+++ b/docs/modules/ROOT/pages/servlet/oauth2/login/logout.adoc
@@ -134,7 +134,7 @@ To enable this, you can stand up the Back-Channel Logout endpoint in the DSL lik
 ======
 Java::
 +
-[source=java,role="primary"]
+[source,java,role="primary"]
 ----
 @Bean
 public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
@@ -152,7 +152,7 @@ public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
 
 Kotlin::
 +
-[source=kotlin,role="secondary"]
+[source,kotlin,role="secondary"]
 ----
 @Bean
 open fun filterChain(http: HttpSecurity): SecurityFilterChain {
@@ -176,7 +176,7 @@ Then, you need a way listen to events published by Spring Security to remove old
 ======
 Java::
 +
-[source=java,role="primary"]
+[source,java,role="primary"]
 ----
 @Bean
 public HttpSessionEventPublisher sessionEventPublisher() {
@@ -186,7 +186,7 @@ public HttpSessionEventPublisher sessionEventPublisher() {
 
 Kotlin::
 +
-[source=kotlin,role="secondary"]
+[source,kotlin,role="secondary"]
 ----
 @Bean
 open fun sessionEventPublisher(): HttpSessionEventPublisher {
@@ -235,7 +235,7 @@ You can achieve this by configuring a custom `OidcSessionRegistry`, like so:
 ======
 Java::
 +
-[source=java,role="primary"]
+[source,java,role="primary"]
 ----
 @Component
 public final class MySpringDataOidcSessionRegistry implements OidcSessionRegistry {
@@ -264,7 +264,7 @@ public final class MySpringDataOidcSessionRegistry implements OidcSessionRegistr
 
 Kotlin::
 +
-[source=kotlin,role="secondary"]
+[source,kotlin,role="secondary"]
 ----
 @Component
 class MySpringDataOidcSessionRegistry: OidcSessionRegistry {