Sync web site with Quarkus documentation

Author: quarkusbot

_generated-doc/latest/infra/quarkus-maven-plugin-goals.adoc

@@ -289,6 +289,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-build-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-build-repoSession]] repoSession
 
 [.description]
@@ -1133,6 +1142,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-deploy-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-deploy-repoSession]] repoSession
 
 [.description]
@@ -1560,6 +1578,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-generate-code-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-generate-code-repoSession]] repoSession
 
 [.description]
@@ -1708,6 +1735,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-generate-code-tests-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-generate-code-tests-repoSession]] repoSession
 
 [.description]
@@ -1995,6 +2031,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-image-build-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-image-build-repoSession]] repoSession
 
 [.description]
@@ -2202,6 +2247,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-image-push-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-image-push-repoSession]] repoSession
 
 [.description]
@@ -2597,6 +2651,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-native-image-agent-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-native-image-agent-repoSession]] repoSession
 
 [.description]
@@ -2736,6 +2799,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-prepare-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-prepare-repoSession]] repoSession
 
 [.description]
@@ -2884,6 +2956,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-prepare-tests-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-prepare-tests-repoSession]] repoSession
 
 [.description]
@@ -3411,6 +3492,15 @@ The properties of the plugin.
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-run-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-run-repoSession]] repoSession
 
 [.description]
@@ -3859,6 +3949,15 @@ a| [[quarkus-maven-plugin-goal-track-config-changes-quarkus.recorded-build-confi
 |`String`
 |
 
+a| [[quarkus-maven-plugin-goal-track-config-changes-reloadPoms]] reloadPoms
+
+[.description]
+--
+POM files from the workspace that should be reloaded from the disk instead of taken from the Maven reactor. This parameter is not supposed to be configured by a user.
+--
+|`Set`
+|
+
 a| [[quarkus-maven-plugin-goal-track-config-changes-repoSession]] repoSession
 
 [.description]

_guides/_attributes.adoc

@@ -1,7 +1,7 @@
 // Common attributes.
 // --> No blank lines (it ends the document header)
 :project-name: Quarkus
-:quarkus-version: 3.21.3
+:quarkus-version: 3.21.4
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.9

_guides/security-oidc-code-flow-authentication.adoc

@@ -1646,6 +1646,64 @@ public class ServiceResource {
 <2> Revoke the authorization code flow access token.
 <3> Revoke the authorization code flow refresh token.
 
+You can also revoke tokens in the security event listeners.
+
+For example, when your application supports a standard <<user-initiated-logout>>, you can catch a logout event and revoke tokens:
+
+[source,java]
+----
+import java.util.concurrent.CompletableFuture;
+import java.util.concurrent.CompletionStage;
+
+import io.quarkus.oidc.AccessTokenCredential;
+import io.quarkus.oidc.OidcProviderClient;
+import io.quarkus.oidc.RefreshToken;
+import io.quarkus.oidc.SecurityEvent;
+import io.quarkus.security.identity.SecurityIdentity;
+import io.smallrye.mutiny.Uni;
+import jakarta.enterprise.context.ApplicationScoped;
+import jakarta.enterprise.event.ObservesAsync;
+
+@ApplicationScoped
+public class SecurityEventListener {
+
+    public CompletionStage<Void> processSecurityEvent(@ObservesAsync SecurityEvent event) {
+        if (SecurityEvent.Type.OIDC_LOGOUT_RP_INITIATED == event.getEventType()) { <1>
+	    return revokeTokens(event.getSecurityIdentity()).subscribeAsCompletionStage();
+	}
+	return CompletableFuture.completedFuture(null);
+    }
+    private Uni<Void> revokeTokens(SecurityIdentity securityIdentity) {
+        return Uni.join().all(
+                   revokeAccessToken(securityIdentity),
+	           revokeRefreshToken(securityIdentity)
+               ).andCollectFailures()
+                .replaceWithVoid()
+                .onFailure().recoverWithUni(t -> logFailure(t));
+    }
+
+    private static Uni<Boolean> revokeAccessToken(SecurityIdentity securityIdentity) { <2>
+        OidcProviderClient oidcProvider = securityIdentity.getAttribute(OidcProviderClient.class.getName());
+        String accessToken = securityIdentity.getCredential(AccessTokenCredential.class).getToken();
+        return oidcProvider.revokeAccessToken(accessToken);
+    }
+
+    private static Uni<Boolean> revokeRefreshToken(SecurityIdentity securityIdentity) { <3>
+        OidcProviderClient oidcProvider = securityIdentity.getAttribute(OidcProviderClient.class.getName());
+        String refreshToken = securityIdentity.getCredential(RefreshToken.class).getToken();
+        return oidcProvider.revokeRefreshToken(refreshToken);
+    }
+
+    private static Uni<Void> logFailure(Throwable t) {
+        // Log failure as required
+        return Uni.createFrom().voidItem();
+    }
+}
+----
+<1> Revoke tokens if an RP-initiated logout event is observed.
+<2> Revoke the authorization code flow access token.
+<3> Revoke the authorization code flow refresh token.
+
 === Propagating tokens to downstream services
 
 For information about Authorization Code Flow access token propagation to downstream services, see the xref:security-openid-connect-client-reference.adoc#token-propagation-rest[Token Propagation] section.

_guides/smallrye-fault-tolerance.adoc

@@ -576,7 +576,7 @@ implementation("io.quarkus:quarkus-smallrye-fault-tolerance")
 == Additional resources
 
 SmallRye Fault Tolerance has more features than shown here.
-Please check the link:https://smallrye.io/docs/smallrye-fault-tolerance/6.9.0/index.html[SmallRye Fault Tolerance documentation] to learn about them.
+Please check the link:https://smallrye.io/docs/smallrye-fault-tolerance/6.9.1/index.html[SmallRye Fault Tolerance documentation] to learn about them.
 
 In Quarkus, you can use the SmallRye Fault Tolerance optional features out of the box.
 
@@ -608,7 +608,7 @@ quarkus.fault-tolerance.mp-compatibility=true
 ----
 ====
 
-The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.9.0/reference/programmatic-api.html[programmatic API] is present and integrated with the declarative, annotation-based API.
+The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.9.1/reference/programmatic-api.html[programmatic API] is present and integrated with the declarative, annotation-based API.
 You can use the `Guard`, `TypedGuard` and `@ApplyGuard` APIs out of the box.
 
 Support for Kotlin is present (assuming you use the Quarkus extension for Kotlin), so you can guard your `suspend` functions with fault tolerance annotations.