KEYCLOAK-5708 Add note that JBoss SSO should not be enabled
This commit is contained in:
parent
08980cfc8e
commit
315e9b8f32
2 changed files with 9 additions and 0 deletions
|
@ -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.
|
||||
|
|
|
@ -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}.
|
Loading…
Reference in a new issue