libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases 1 Packages Activity Actions

KEYCLOAK-5708 Add note that JBoss SSO should not be enabled

Browse source
This commit is contained in:
stianst 2017-12-05 10:27:11 +01:00 committed by Stian Thorgersen
parent 08980cfc8e
commit 315e9b8f32
2 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
securing_apps/topics/oidc/java/jboss-adapter.adoc
View file

@ -227,6 +227,11 @@ endif::[]
$ ./bin/jboss-cli.sh --file=adapter-install.cli $ ./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 ===== Required Per WAR Configuration
This section describes how to secure a WAR directly by adding configuration and editing files within your WAR package. This section describes how to secure a WAR directly by adding configuration and editing files within your WAR package.

4
securing_apps/topics/saml/java/jboss-adapter/jboss_adapter_installation.adoc
View file

@ -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 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. `@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}.