Auth with both webUI and CLI doesn't work with quarkus-keycloak

guides/common/modules/proc_registering-project-as-a-client-of-keycloak.adoc

@@ -1,9 +1,20 @@
 [id="registering-{project-context}-as-a-client-of-keycloak_{context}"]
 = Registering {Project} as a client of {keycloak}
 
+ifeval::["{context}" == "keycloak-quarkus"]
+Users defined in {keycloak} can authenticate to {Project} by using one of the following methods:
+
+* The {ProjectWebUI}
+* Hammer CLI
+
+Choose one of these methods to enable in your {Project} deployment.
+endif::[]
+
+ifeval::["{context}" == "keycloak-wildfly"]
 Users defined in {keycloak} can authenticate to {Project} by using the {ProjectWebUI} or by using Hammer CLI.
 Each authentication method requires you to register a separate {Project} client to {keycloak}.
 If you want users to authenticate by using both {ProjectWebUI} and Hammer CLI, you must register two different {Project} clients to {keycloak}.
+endif::[]
 
 .Procedure
 
@@ -16,7 +27,8 @@ On your {ProjectServer}:
 # {project-package-install} mod_auth_openidc keycloak-httpd-client-install python3-lxml
 ----
 // python3-lxml is only needed on EL8 because of https://issues.redhat.com/browse/RHEL-31496
-. If you want users to authenticate by using the {ProjectWebUI}:
+. Choose the authentication method you want {keycloak} users to use when authenticating to {Project}:
+* If you want users to authenticate by using the {ProjectWebUI}:
 .. Create a client for {Project}.
 Use `foreman-openidc` as the application name.
 +
@@ -38,7 +50,7 @@ Use `foreman-openidc` as the application name.
 --foreman-keycloak-app-name "foreman-openidc" \
 --foreman-keycloak-realm "_{Project}_Realm_"
 ----
-. If you want users to authenticate by using the Hammer CLI, create a client for {Project}.
+* If you want users to authenticate by using the Hammer CLI, create a client for {Project}.
 Use `hammer-openidc` as the application name.
 +
 [options="nowrap", subs="verbatim,quotes,attributes"]