diff --git a/topics/oidc/java/jboss-adapter.adoc b/topics/oidc/java/jboss-adapter.adoc index 00bcc5c3a5..ddc6a4fa03 100755 --- a/topics/oidc/java/jboss-adapter.adoc +++ b/topics/oidc/java/jboss-adapter.adoc @@ -174,7 +174,9 @@ public class CustomerService { This section describes how to secure a WAR directly by adding config and editing files within your WAR package. The first thing you must do is create a `keycloak.json` adapter config file within the `WEB-INF` directory of your WAR. -The format of this config file is describe in the <<_java_adapter_config,general adapter configuration>> section. + +The format of this config file is describe in the <> section. + Next you must set the `auth-method` to `KEYCLOAK` in `web.xml`. You also have to use standard servlet security to specify role-base constraints on your URLs. @@ -259,7 +261,9 @@ This metadata is instead defined within server configuration (i.e. `standalone.x The `secure-deployment` `name` attribute identifies the WAR you want to secure. Its value is the `module-name` defined in `web.xml` with `.war` appended. -The rest of the configuration corresponds pretty much one to one with the `keycloak.json` configuration options defined in <<_java_adapter_config,general adapter configuration>>. + +The rest of the configuration corresponds pretty much one to one with the `keycloak.json` configuration options defined in <>. + The exception is the `credential` element. To make it easier for you, you can go to the {{book.project.title}} Administration Console and go to the Application/Installation tab of the application this WAR is aligned with. diff --git a/topics/oidc/java/jetty8-adapter.adoc b/topics/oidc/java/jetty8-adapter.adoc index 2ccd38bd0d..1c18438e2f 100755 --- a/topics/oidc/java/jetty8-adapter.adoc +++ b/topics/oidc/java/jetty8-adapter.adoc @@ -44,4 +44,4 @@ OPTIONS=Server,jsp,jmx,resources,websocket,ext,plus,annotations,keycloak Enabling Keycloak for your WARs is the same as the Jetty 9.x adapter. Our 8.1.x adapter supports both keycloak.json and the jboss-web.xml advanced configuration. -See <<_jetty9_per_war,Required Per WAR Configuration>> \ No newline at end of file +See <> \ No newline at end of file diff --git a/topics/oidc/java/jetty9-adapter.adoc b/topics/oidc/java/jetty9-adapter.adoc index 1f3017e726..ca21ecf29e 100755 --- a/topics/oidc/java/jetty9-adapter.adoc +++ b/topics/oidc/java/jetty9-adapter.adoc @@ -57,7 +57,9 @@ This is a Jetty specific config file and you must define a Keycloak specific aut ---- Next you must create a `keycloak.json` adapter config file within the `WEB-INF` directory of your WAR. -The format of this config file is describe in the <<_java_adapter_config,general adapter configuration>> section. + +The format of this config file is describe in the <> section. + WARNING: The Jetty 9.1.x adapter will not be able to find the `keycloak.json` file. You will have to define all adapter settings within the `jetty-web.xml` file as described below. diff --git a/topics/oidc/java/spring-security-adapter.adoc b/topics/oidc/java/spring-security-adapter.adoc index 84e8b6c3ad..d0a895caca 100755 --- a/topics/oidc/java/spring-security-adapter.adoc +++ b/topics/oidc/java/spring-security-adapter.adoc @@ -152,7 +152,7 @@ While Spring Security's XML namespace simplifies configuration, customizing the The Keycloak Spring Security adapter also supports multi tenancy. Instead of injecting `AdapterDeploymentContextFactoryBean` with the path to `keycloak.json` you can inject an implementation of the `KeycloakConfigResolver` interface. -More details on how to implement the `KeycloakConfigResolver` can be found in <<_multi_tenancy>>. +More details on how to implement the `KeycloakConfigResolver` can be found in <>. ==== Naming Security Roles diff --git a/topics/oidc/java/tomcat-adapter.adoc b/topics/oidc/java/tomcat-adapter.adoc index 1b7f6ca7de..d978d4901b 100755 --- a/topics/oidc/java/tomcat-adapter.adoc +++ b/topics/oidc/java/tomcat-adapter.adoc @@ -45,7 +45,9 @@ This is a Tomcat specific config file and you must define a Keycloak specific Va ---- Next you must create a `keycloak.json` adapter config file within the `WEB-INF` directory of your WAR. -The format of this config file is describe in the <<_java_adapter_config,general adapter configuration>> section. + +The format of this config file is describe in the <> section. + Finally you must specify both a `login-config` and use standard servlet security to specify role-base constraints on your URLs. Here's an example: