KEYCLOAK-1414 Add CLI script for installing JBoss/WildFly/EAP adapters.
This commit is contained in:
parent
5695677873
commit
092562fb94
6 changed files with 38 additions and 2 deletions
|
@ -27,4 +27,10 @@
|
||||||
<outputDirectory>modules</outputDirectory>
|
<outputDirectory>modules</outputDirectory>
|
||||||
</fileSet>
|
</fileSet>
|
||||||
</fileSets>
|
</fileSets>
|
||||||
|
<files>
|
||||||
|
<file>
|
||||||
|
<source>../../shared-cli/adapter-install.cli</source>
|
||||||
|
<outputDirectory>bin</outputDirectory>
|
||||||
|
</file>
|
||||||
|
</files>
|
||||||
</assembly>
|
</assembly>
|
||||||
|
|
|
@ -27,4 +27,10 @@
|
||||||
<outputDirectory>modules/system/layers/base</outputDirectory>
|
<outputDirectory>modules/system/layers/base</outputDirectory>
|
||||||
</fileSet>
|
</fileSet>
|
||||||
</fileSets>
|
</fileSets>
|
||||||
|
<files>
|
||||||
|
<file>
|
||||||
|
<source>../../shared-cli/adapter-install.cli</source>
|
||||||
|
<outputDirectory>bin</outputDirectory>
|
||||||
|
</file>
|
||||||
|
</files>
|
||||||
</assembly>
|
</assembly>
|
||||||
|
|
4
distribution/adapters/shared-cli/adapter-install.cli
Normal file
4
distribution/adapters/shared-cli/adapter-install.cli
Normal file
|
@ -0,0 +1,4 @@
|
||||||
|
/subsystem=security/security-domain=keycloak/:add
|
||||||
|
/subsystem=security/security-domain=keycloak/authentication=classic/:add(login-modules=[{ "code" => "org.keycloak.adapters.jboss.KeycloakLoginModule","flag" => "required"}])
|
||||||
|
/extension=org.keycloak.keycloak-adapter-subsystem/:add(module=org.keycloak.keycloak-adapter-subsystem)
|
||||||
|
/subsystem=keycloak:add
|
|
@ -28,4 +28,10 @@
|
||||||
<outputDirectory>modules/system/layers/base</outputDirectory>
|
<outputDirectory>modules/system/layers/base</outputDirectory>
|
||||||
</fileSet>
|
</fileSet>
|
||||||
</fileSets>
|
</fileSets>
|
||||||
|
<files>
|
||||||
|
<file>
|
||||||
|
<source>../../shared-cli/adapter-install.cli</source>
|
||||||
|
<outputDirectory>bin</outputDirectory>
|
||||||
|
</file>
|
||||||
|
</files>
|
||||||
</assembly>
|
</assembly>
|
||||||
|
|
|
@ -27,4 +27,10 @@
|
||||||
<outputDirectory>modules/system/layers/base</outputDirectory>
|
<outputDirectory>modules/system/layers/base</outputDirectory>
|
||||||
</fileSet>
|
</fileSet>
|
||||||
</fileSets>
|
</fileSets>
|
||||||
|
<files>
|
||||||
|
<file>
|
||||||
|
<source>../../shared-cli/adapter-install.cli</source>
|
||||||
|
<outputDirectory>bin</outputDirectory>
|
||||||
|
</file>
|
||||||
|
</files>
|
||||||
</assembly>
|
</assembly>
|
||||||
|
|
|
@ -48,6 +48,15 @@ $ unzip keycloak-as7-adapter-dist.zip
|
||||||
After adding the Keycloak modules, you must then enable the Keycloak Subsystem within your app server's server configuration:
|
After adding the Keycloak modules, you must then enable the Keycloak Subsystem within your app server's server configuration:
|
||||||
<literal>domain.xml</literal> or <literal>standalone.xml</literal>.
|
<literal>domain.xml</literal> or <literal>standalone.xml</literal>.
|
||||||
</para>
|
</para>
|
||||||
|
<para>
|
||||||
|
There is a CLI script that will help you modify your server configuration. Start the server and run the script
|
||||||
|
from the server's bin directory:
|
||||||
|
<programlisting>
|
||||||
|
$ cd $JBOSS_HOME/bin
|
||||||
|
$ jboss-cli.sh -c --file=adapter-install.cli
|
||||||
|
</programlisting>
|
||||||
|
The script will add the extension, subsystem, and optional security-domain as described below.
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
<programlisting><![CDATA[
|
<programlisting><![CDATA[
|
||||||
<server xmlns="urn:jboss:domain:1.4">
|
<server xmlns="urn:jboss:domain:1.4">
|
||||||
|
@ -65,8 +74,7 @@ $ unzip keycloak-as7-adapter-dist.zip
|
||||||
</programlisting>
|
</programlisting>
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
Finally, you must specify a shared keycloak security domain.
|
The keycloak security domain should be used with EJBs and other components when you need the security context created
|
||||||
This security domain should be used with EJBs and other components when you need the security context created
|
|
||||||
in the secured web tier to be propagated to the EJBs (other EE component) you are invoking. Otherwise
|
in the secured web tier to be propagated to the EJBs (other EE component) you are invoking. Otherwise
|
||||||
this configuration is optional.
|
this configuration is optional.
|
||||||
</para>
|
</para>
|
||||||
|
|
Loading…
Reference in a new issue