Sync documentation of main branch

Author: actions-user

_generated-doc/main/config/quarkus-all-config.adoc

@@ -26599,6 +26599,27 @@ endif::add-copy-button-to-env-var[]
 a|`password`, `client-credentials`
 |`password`
 
+a| [[quarkus-keycloak-admin-client_quarkus-keycloak-admin-client-tls-configuration-name]] [.property-path]##`quarkus.keycloak.admin-client.tls-configuration-name`##
+
+[.description]
+--
+The name of the TLS configuration to use.
+
+If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown.
+
+The default TLS configuration is *not* used by default.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_KEYCLOAK_ADMIN_CLIENT_TLS_CONFIGURATION_NAME+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_KEYCLOAK_ADMIN_CLIENT_TLS_CONFIGURATION_NAME+++`
+endif::add-copy-button-to-env-var[]
+--
+|string
+|
+
 
 h|[.extension-name]##Keycloak Authorization##
 h|Type
@@ -51461,7 +51482,7 @@ endif::add-copy-button-to-env-var[]
 |
 
 
-h|[.extension-name]##Observability Dev Services##
+h|[.extension-name]##Observability##
 h|Type
 h|Default
 

_generated-doc/main/config/quarkus-keycloak-admin-client.adoc

@@ -161,6 +161,27 @@ endif::add-copy-button-to-env-var[]
 a|`password`, `client-credentials`
 |`password`
 
+a| [[quarkus-keycloak-admin-client_quarkus-keycloak-admin-client-tls-configuration-name]] [.property-path]##`quarkus.keycloak.admin-client.tls-configuration-name`##
+
+[.description]
+--
+The name of the TLS configuration to use.
+
+If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown.
+
+The default TLS configuration is *not* used by default.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_KEYCLOAK_ADMIN_CLIENT_TLS_CONFIGURATION_NAME+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_KEYCLOAK_ADMIN_CLIENT_TLS_CONFIGURATION_NAME+++`
+endif::add-copy-button-to-env-var[]
+--
+|string
+|
+
 |===
 
 

_generated-doc/main/config/quarkus-keycloak-admin-client_quarkus.keycloak.adoc

@@ -161,6 +161,27 @@ endif::add-copy-button-to-env-var[]
 a|`password`, `client-credentials`
 |`password`
 
+a| [[quarkus-keycloak-admin-client_quarkus-keycloak-admin-client-tls-configuration-name]] [.property-path]##`quarkus.keycloak.admin-client.tls-configuration-name`##
+
+[.description]
+--
+The name of the TLS configuration to use.
+
+If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown.
+
+The default TLS configuration is *not* used by default.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_KEYCLOAK_ADMIN_CLIENT_TLS_CONFIGURATION_NAME+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_KEYCLOAK_ADMIN_CLIENT_TLS_CONFIGURATION_NAME+++`
+endif::add-copy-button-to-env-var[]
+--
+|string
+|
+
 |===
 
 

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

@@ -5644,6 +5644,25 @@ Build item to specify the minimal required `io.netty.allocator.maxOrder`. Quarku
 _No Javadoc found_
 
 
+|===
+== Observability Dev Services
+[.configuration-reference,cols=2*]
+|===
+h|Class Name
+h|Attributes 
+
+
+
+
+a| https://github.com/quarkusio/quarkus/blob/main/extensions/observability-devservices/deployment/src/main/java/io/quarkus/observability/deployment/devui/ObservabilityDevServicesConfigBuildItem.java[`io.quarkus.observability.deployment.devui.ObservabilityDevServicesConfigBuildItem`, window="_blank"]
+[.description]
+--
+Build item used to carry running DevService values to Dev UI.
+-- a|`java.util.Map<String,String> config` 
+
+_No Javadoc found_
+
+
 |===
 == OpenID Connect Adapter
 [.configuration-reference,cols=2*]

_versions/main/guides/images/dev-ui-observability-card.png

@@ -97,6 +97,10 @@ If you miss the message you can always check the port with this Docker command:
 docker ps | grep grafana
 ----
 
+Another option is to use the Dev UI as the Grafana URL link will be available and if selected will open a new browser tab directly to the running Grafana instance:
+
+image::dev-ui-observability-card.png[alt=Dev UI LGTM, align=center,width=80%]
+
 === Additional configuration
 
 This extension will configure your `quarkus-opentelemetry` and `quarkus-micrometer-registry-otlp` extensions to send data to the OTel Collector bundled with the Grafana OTel LGTM image.

_versions/main/guides/observability-devservices-lgtm.adoc

@@ -195,6 +195,20 @@ quarkus.keycloak.admin-client.grant-type=CLIENT_CREDENTIALS <1>
 
 NOTE: Note that the xref:security-openid-connect-client.adoc[OidcClient] can also be used to acquire tokens.
 
+== Configuring TLS
+
+To configure a TLS connection for the Keycloak Admin Client, use the TLS Registry extension and point the Keycloak Admin Client to respective TLS configuration.
+For example, you can configure mutual TLS (mTLS) like this:
+
+[source,properties]
+----
+quarkus.keycloak.admin-client.tls-configuration-name=kc-mtls
+quarkus.tls.kc-mtls.key-store.p12.path=client-keystore.p12
+quarkus.tls.kc-mtls.key-store.p12.password=secret
+quarkus.tls.kc-mtls.trust-store.p12.path=client-truststore.p12
+quarkus.tls.kc-mtls.trust-store.p12.password=secret
+----
+
 == Testing
 
 The preferred approach for testing Keycloak Admin Client against Keycloak is xref:security-openid-connect-dev-services.adoc[Dev Services for Keycloak].

_versions/main/guides/security-keycloak-admin-client.adoc

@@ -25,7 +25,7 @@ The TLS Registry extension is automatically included in your project when you us
 As a result, applications that use the TLS Registry can be ready to handle secure communications out of the box.
 TLS Registry also provides features like automatic certificate reloading, Let's Encrypt (ACME) integration, Kubernetes Cert-Manager support, and compatibility with various keystore formats, such as PKCS12, PEM, and JKS.
 
-[#using-the-tls-registry]
+[[using-the-tls-registry]]
 == Using the TLS registry
 
 To configure a TLS connection, including key and truststores, use the `+quarkus.tls.*+` properties.
@@ -126,7 +126,7 @@ quarkus.grpc.server.plain-text=false
 +
 This configuration enables mTLS by ensuring that both the server and client validate each other's certificates, which provides an additional layer of security.
 
-[#referencing-a-tls-configuration]
+[[referencing-a-tls-configuration]]
 == Referencing a TLS configuration
 
 To reference an example  _named_ configuration that you created by using the `quarkus.tls.<name>.*` properties as explained in <<using-the-tls-registry>>
@@ -257,7 +257,7 @@ quarkus.tls.key-store.jks.alias-password=my-alias-password
 * Alternatively, use SNI to select the appropriate certificate and private key.
 Note that all keys must use the same password.
 
-[#sni]
+[[sni]]
 ==== SNI
 
 Server Name Indication (SNI) is a TLS extension that makes it possible for a client to specify the host name to which it attempts to connect during the TLS handshake.
@@ -585,7 +585,7 @@ When an application that uses the TLS extension starts, the TLS registry perform
 
 If any of these checks fail, the application will not start.
 
-[#reloading-certificates]
+[[reloading-certificates]]
 == Reloading certificates
 
 The `TlsConfiguration` obtained from the `TLSConfigurationRegistry` includes a mechanism for reloading certificates.
@@ -1267,12 +1267,11 @@ quarkus.http.insecure-requests=redirect
 
 ====
 
-[[lets-encrypt-prepare]]
-
 The challenge is served from the primary HTTP interface (accessible from your DNS domain name).
 
 IMPORTANT: Do not start your application yet.
 
+[[lets-encrypt-prepare]]
 === Application preparation
 
 Before you request a Let's Encrypt certificate: