diff --git a/topics/saml/java/jetty-adapter/jetty8-per_war_config.adoc b/topics/saml/java/jetty-adapter/jetty8-per_war_config.adoc index 75b5381438..90f66c7c57 100644 --- a/topics/saml/java/jetty-adapter/jetty8-per_war_config.adoc +++ b/topics/saml/java/jetty-adapter/jetty8-per_war_config.adoc @@ -2,4 +2,4 @@ ===== Jetty 8 Per WAR Configuration Enabling Keycloak for your WARs is the same as the Jetty 9.x adapter. -See <> +See <> diff --git a/topics/saml/java/servlet-filter-adapter.adoc b/topics/saml/java/servlet-filter-adapter.adoc index f8c3ab5a02..f377f4f4b2 100644 --- a/topics/saml/java/servlet-filter-adapter.adoc +++ b/topics/saml/java/servlet-filter-adapter.adoc @@ -4,7 +4,9 @@ If you want to use SAML with a Java servlet application that doesn't have an adapter for that servlet platform, you can opt to use the servlet filter adapter that {{book.project.name}} has. This adapter works a little differently than the other adapters. -You do not define security constraints in web.xml. +You still have to specify a `/WEB-INF/keycloak-saml.xml` file as defined in +the <> section, but +you do not define security constraints in _web.xml_. Instead you define a filter mapping using the {{book.project.name}} servlet filter adapter to secure the url patterns you want to secure. NOTE: Backchannel logout works a bit differently than the standard adapters. diff --git a/topics/saml/java/tomcat-adapter/tomcat_adapter_per_war_config.adoc b/topics/saml/java/tomcat-adapter/tomcat_adapter_per_war_config.adoc index 7b63cc8068..3ea4a65066 100644 --- a/topics/saml/java/tomcat-adapter/tomcat_adapter_per_war_config.adoc +++ b/topics/saml/java/tomcat-adapter/tomcat_adapter_per_war_config.adoc @@ -14,7 +14,7 @@ This is a Tomcat specific config file and you must define a Keycloak specific Va ---- Next you must create a `keycloak-saml.xml` adapter config file within the `WEB-INF` directory of your WAR. -The format of this config file is describe in the <<> 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: