Sync documentation of main branch

Author: actions-user

_generated-doc/main/infra/quarkus-all-build-items.adoc

@@ -140,7 +140,15 @@ _No Javadoc found_
 a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/builditem/ApplicationInfoBuildItem.java[`io.quarkus.deployment.builditem.ApplicationInfoBuildItem`, window="_blank"]
 [.description]
 --
-_No Javadoc found_
+This build item holds essential metadata about the application, specifically its name and version. The values can be configured using the following properties: 
+
+*  `quarkus.application.name` - Sets the application name
+
+
+*  `quarkus.application.version` - Sets the application version
+
+
+This configuration is intended to be used by extensions that require application metadata, such as the kubernetes extension.
 -- a|`java.lang.String name` 
 
 _No Javadoc found_
@@ -2054,8 +2062,21 @@ a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/
 Attempts to register a complete type hierarchy for reflection. 
 This is intended to be used to register types that are going to be serialized, e.g. by Jackson or some other JSON mapper. 
 This will do 'smart discovery' and in addition to registering the type itself it will also attempt to register the following: 
-- Superclasses - Subclasses - Component types of collections - Types used in bean properties (if method reflection is enabled) - Field types (if field reflection is enabled) 
-This discovery is applied recursively, so any additional types that are registered will also have their dependencies discovered
+
+* Superclasses
+
+
+* Component types of collections
+
+
+* Types used in bean properties (if method reflection is enabled)
+
+
+* Field types (if field reflection is enabled)
+
+
+
+This discovery is applied recursively, so any additional types that are registered will also have their dependencies discovered.
 -- a|`org.jboss.jandex.Type type` 
 
 _No Javadoc found_

_versions/main/guides/security-oidc-code-flow-authentication.adoc

@@ -1655,6 +1655,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.