From 878fd16dd7325bf4823640b174da64563aa2b68c Mon Sep 17 00:00:00 2001 From: Erik Jan de Wit Date: Mon, 27 Feb 2023 15:04:01 +0100 Subject: [PATCH] removed use of installation tab (#1778) * removed use of installation tab fixes: https://github.com/keycloak/keycloak/issues/17146 * Update securing_apps/topics/docker/docker-overview.adoc Co-authored-by: andymunro <48995441+andymunro@users.noreply.github.com> * Update securing_apps/topics/oidc/java/jboss-adapter.adoc Co-authored-by: andymunro <48995441+andymunro@users.noreply.github.com> * Update server_admin/topics/clients/oidc/con-audience.adoc Co-authored-by: andymunro <48995441+andymunro@users.noreply.github.com> --------- Co-authored-by: andymunro <48995441+andymunro@users.noreply.github.com> --- securing_apps/topics/docker/docker-overview.adoc | 6 +++--- securing_apps/topics/oidc/java/jboss-adapter.adoc | 2 +- server_admin/topics/clients/oidc/con-audience.adoc | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/securing_apps/topics/docker/docker-overview.adoc b/securing_apps/topics/docker/docker-overview.adoc index db1e4a0263..fd04d4b2b9 100644 --- a/securing_apps/topics/docker/docker-overview.adoc +++ b/securing_apps/topics/docker/docker-overview.adoc @@ -29,7 +29,7 @@ WARNING: Don't forget to configure the `rootcertbundle` field with the location === Docker registry environment variable override installation -Often times it is appropriate to use a simple environment variable override for develop or POC Docker registries. While this approach is usually not recommended for production use, it can be helpful when one requires quick-and-dirty way to stand up a registry. Simply use the _Variable Override_ Format Option from the client installation tab, and an output should appear like the one below: +Often times it is appropriate to use a simple environment variable override for develop or POC Docker registries. While this approach is usually not recommended for production use, it can be helpful when one requires quick-and-dirty way to stand up a registry. Simply use the _Variable Override_ Format Option from the client details, and an output should appear like the one below: [source,subs="attributes+"] ---- @@ -49,8 +49,8 @@ The zip file installation mechanism provides a quickstart for developers who wan .Procedure -1. From the desired realm, create a client configuration. At this point you won't have a Docker registry - the quickstart will take care of that part. - 2. Choose the "Docker Compose YAML" option from the installation tab and download the .zip file + 1. From the desired realm, create a client configuration. At this point you will not have a Docker registry - the quickstart will take care of that part. + 2. Choose the "Docker Compose YAML" option from the from _Action_ menu and select the *Download adapter config* option to download the ZIP file. 3. Unzip the archive to the desired location, and open the directory. 4. Start the Docker registry with `docker-compose up` diff --git a/securing_apps/topics/oidc/java/jboss-adapter.adoc b/securing_apps/topics/oidc/java/jboss-adapter.adoc index ebe9e39baf..f716a3f545 100644 --- a/securing_apps/topics/oidc/java/jboss-adapter.adoc +++ b/securing_apps/topics/oidc/java/jboss-adapter.adoc @@ -223,7 +223,7 @@ Its value is the `module-name` defined in `web.xml` with `.war` appended. The re The exception is the `credential` element. -To make it easier for you, you can go to the {project_name} Admin Console and go to the Client/Installation tab of the application this WAR is aligned with. +To simplify this change, log into the Admin Console and go to the Client details of the application this WAR is aligned with. Then, from the _Action_ menu, select the *Download adapter config* option. It provides an example XML file you can cut and paste. If you have multiple deployments secured by the same realm you can share the realm configuration in a separate element. For example: diff --git a/server_admin/topics/clients/oidc/con-audience.adoc b/server_admin/topics/clients/oidc/con-audience.adoc index 54f281ed46..320032fece 100644 --- a/server_admin/topics/clients/oidc/con-audience.adoc +++ b/server_admin/topics/clients/oidc/con-audience.adoc @@ -95,7 +95,7 @@ For more control over the protocol mapper, you can create the protocol mapper on .Audience protocol mapper image:images/audience_mapper.png[] -* From the <<_client_installation, Installation tab>> of the *good-service* client, you can generate the adapter configuration and you can confirm that _verify-token-audience_ option will be set to *true*. This forces the adapter to verify the audience if you use this configuration. +* From the <<_client_installation, Client details tab>> of the *good-service* client, you can generate the adapter configuration and confirm that _verify-token-audience_ is set to *true*. This action forces the adapter to verify the audience if you use this configuration. * You need to ensure that the confidential client is able to request *good-service* as an audience in its tokens. +