2016-12-12 16:01:26 +00:00
|
|
|
[[_saml_jboss_adapter]]
|
2016-06-02 16:07:45 +00:00
|
|
|
|
2016-06-10 11:05:56 +00:00
|
|
|
{% if book.community %}
|
|
|
|
|
==== JBoss EAP/Wildfly Adapter
|
|
|
|
|
{% endif %}
|
|
|
|
|
{% if book.product %}
|
|
|
|
|
==== JBoss EAP Adapter
|
|
|
|
|
{% endif %}
|
2016-06-02 16:07:45 +00:00
|
|
|
|
2016-06-10 11:08:00 +00:00
|
|
|
{% if book.community %}
|
|
|
|
|
To be able to secure WAR apps deployed on JBoss EAP or Wildfly, you must install and configure the {{book.project.name}} SAML Adapter Subsystem.
|
|
|
|
|
{% endif %}
|
|
|
|
|
{% if book.product %}
|
|
|
|
|
To be able to secure WAR apps deployed on JBoss EAP, you must install and configure the {{book.project.name}} SAML Adapter Subsystem.
|
|
|
|
|
{% endif %}
|
|
|
|
|
|
2016-06-02 16:07:45 +00:00
|
|
|
You then provide a keycloak config, `/WEB-INF/keycloak-saml.xml` file in your WAR and change the auth-method to KEYCLOAK-SAML within web.xml.
|
2016-11-29 22:15:51 +00:00
|
|
|
Both methods are described in this section.
|
