This commit is contained in:
Bill Burke 2016-06-02 18:04:37 -04:00
parent 2439546f24
commit 849414d158
3 changed files with 5 additions and 3 deletions

View file

@ -2,4 +2,4 @@
===== Jetty 8 Per WAR Configuration ===== Jetty 8 Per WAR Configuration
Enabling Keycloak for your WARs is the same as the Jetty 9.x adapter. Enabling Keycloak for your WARs is the same as the Jetty 9.x adapter.
See <<fake/../../../../saml/java/jetty-adapter/jetty9_per_war_config.adoc#_saml-jetty9-per-war,Per War Configuration>> See <<fake/../../../../saml/java/jetty-adapter/jetty9_per_war_config.adoc#_saml-jetty9-per-war, Jetty 9 Per War Configuration>>

View file

@ -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 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. opt to use the servlet filter adapter that {{book.project.name}} has.
This adapter works a little differently than the other adapters. 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 <<fake/../../../../saml/java/general-config.adoc#_saml-general-config,General Adapter Config>> 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. 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. NOTE: Backchannel logout works a bit differently than the standard adapters.

View file

@ -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. 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 <<<fake/../../../../saml/java/general-config.adoc#_saml-general-config,General Adapter Config>> section. The format of this config file is describe in the <<fake/../../../../saml/java/general-config.adoc#_saml-general-config,General Adapter Config>> section.
Finally you must specify both a `login-config` and use standard servlet security to specify role-base constraints on your URLs. 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: Here's an example: