2019-01-21 17:01:40 +00:00
|
|
|
[[_saml_jboss_adapter]]
|
2016-06-02 16:07:45 +00:00
|
|
|
|
2017-08-28 12:50:14 +00:00
|
|
|
ifeval::[{project_community}==true]
|
2018-05-29 08:02:18 +00:00
|
|
|
==== JBoss EAP/WildFly Adapter
|
2017-08-28 12:50:14 +00:00
|
|
|
endif::[]
|
|
|
|
|
ifeval::[{project_product}==true]
|
2016-06-10 11:05:56 +00:00
|
|
|
==== JBoss EAP Adapter
|
2017-08-28 12:50:14 +00:00
|
|
|
endif::[]
|
2016-06-02 16:07:45 +00:00
|
|
|
|
2017-08-28 12:50:14 +00:00
|
|
|
ifeval::[{project_community}==true]
|
2018-05-29 08:02:18 +00:00
|
|
|
To be able to secure WAR apps deployed on JBoss EAP or WildFly, you must install and configure the {project_name} SAML Adapter Subsystem.
|
2017-08-28 12:50:14 +00:00
|
|
|
endif::[]
|
|
|
|
|
ifeval::[{project_product}==true]
|
|
|
|
|
To be able to secure WAR apps deployed on JBoss EAP, you must install and configure the {project_name} SAML Adapter Subsystem.
|
|
|
|
|
endif::[]
|
2016-06-10 11:08:00 +00:00
|
|
|
|
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.
|
