From 315e9b8f325f9e40450311457a9eca1b351afb14 Mon Sep 17 00:00:00 2001 From: stianst Date: Tue, 5 Dec 2017 10:27:11 +0100 Subject: [PATCH] KEYCLOAK-5708 Add note that JBoss SSO should not be enabled --- securing_apps/topics/oidc/java/jboss-adapter.adoc | 5 +++++ .../saml/java/jboss-adapter/jboss_adapter_installation.adoc | 4 ++++ 2 files changed, 9 insertions(+) diff --git a/securing_apps/topics/oidc/java/jboss-adapter.adoc b/securing_apps/topics/oidc/java/jboss-adapter.adoc index 4f392db710..6c386348d9 100644 --- a/securing_apps/topics/oidc/java/jboss-adapter.adoc +++ b/securing_apps/topics/oidc/java/jboss-adapter.adoc @@ -227,6 +227,11 @@ endif::[] $ ./bin/jboss-cli.sh --file=adapter-install.cli ---- +===== JBoss SSO + +{appserver_name} has built-in support for single sign-on for web applications deployed to the same {appserver_name} +instance. This should not be enabled when using {project_name}. + ===== Required Per WAR Configuration This section describes how to secure a WAR directly by adding configuration and editing files within your WAR package. diff --git a/securing_apps/topics/saml/java/jboss-adapter/jboss_adapter_installation.adoc b/securing_apps/topics/saml/java/jboss-adapter/jboss_adapter_installation.adoc index 1c328bebea..e5ea6a0f9c 100644 --- a/securing_apps/topics/saml/java/jboss-adapter/jboss_adapter_installation.adoc +++ b/securing_apps/topics/saml/java/jboss-adapter/jboss_adapter_installation.adoc @@ -143,3 +143,7 @@ public class CustomerService { We hope to improve our integration in the future so that you don't have to specify the `@SecurityDomain` annotation when you want to propagate a keycloak security context to the EJB tier. +===== JBoss SSO + +{appserver_name} has built-in support for single sign-on for web applications deployed to the same {appserver_name} +instance. This should not be enabled when using {project_name}. \ No newline at end of file