jetty 8 docs
This commit is contained in:
parent
eccb295076
commit
9a622a05b1
3 changed files with 50 additions and 1 deletions
|
@ -13,6 +13,7 @@
|
||||||
<!ENTITY JavascriptAdapter SYSTEM "modules/javascript-adapter.xml">
|
<!ENTITY JavascriptAdapter SYSTEM "modules/javascript-adapter.xml">
|
||||||
<!ENTITY TomcatAdapter SYSTEM "modules/tomcat-adapter.xml">
|
<!ENTITY TomcatAdapter SYSTEM "modules/tomcat-adapter.xml">
|
||||||
<!ENTITY Jetty9Adapter SYSTEM "modules/jetty9-adapter.xml">
|
<!ENTITY Jetty9Adapter SYSTEM "modules/jetty9-adapter.xml">
|
||||||
|
<!ENTITY Jetty8Adapter SYSTEM "modules/jetty8-adapter.xml">
|
||||||
<!ENTITY InstalledApplications SYSTEM "modules/installed-applications.xml">
|
<!ENTITY InstalledApplications SYSTEM "modules/installed-applications.xml">
|
||||||
<!ENTITY Logout SYSTEM "modules/logout.xml">
|
<!ENTITY Logout SYSTEM "modules/logout.xml">
|
||||||
<!ENTITY SAML SYSTEM "modules/saml.xml">
|
<!ENTITY SAML SYSTEM "modules/saml.xml">
|
||||||
|
@ -88,6 +89,7 @@ This one is short
|
||||||
&JBossAdapter;
|
&JBossAdapter;
|
||||||
&TomcatAdapter;
|
&TomcatAdapter;
|
||||||
&Jetty9Adapter;
|
&Jetty9Adapter;
|
||||||
|
&Jetty8Adapter;
|
||||||
&JavascriptAdapter;
|
&JavascriptAdapter;
|
||||||
&InstalledApplications;
|
&InstalledApplications;
|
||||||
&Logout;
|
&Logout;
|
||||||
|
|
47
docbook/reference/en/en-US/modules/jetty8-adapter.xml
Executable file
47
docbook/reference/en/en-US/modules/jetty8-adapter.xml
Executable file
|
@ -0,0 +1,47 @@
|
||||||
|
<section id="jetty8-adapter">
|
||||||
|
<title>Jetty 8.1.x Adapter</title>
|
||||||
|
<para>
|
||||||
|
Keycloak has a separate adapter for Jetty 8.1.x that you will have to install into your Jetty
|
||||||
|
installation. You then have to provide some extra configuration in each WAR you deploy to
|
||||||
|
Jetty. Let's go over these steps.
|
||||||
|
</para>
|
||||||
|
<section id="jetty8-adapter-installation">
|
||||||
|
<title>Adapter Installation</title>
|
||||||
|
<para>
|
||||||
|
There is a adapter zip file for Jetty 8.1.x in the <literal>adapters/</literal> directory in the Keycloak appliance
|
||||||
|
or war distribution. You must unzip this file into Jetty 8.1.x's root directory. Including
|
||||||
|
adapter's jars within your WEB-INF/lib directory will not work!
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
<programlisting>
|
||||||
|
$ cd $JETTY_HOME
|
||||||
|
$ unzip keycloak-jetty81-adapter-dist.zip
|
||||||
|
</programlisting>
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
Next, you will have to enable the keycloak option. Edit start.ini and add keycloak to the options
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
<programlisting>
|
||||||
|
<![CDATA[
|
||||||
|
#===========================================================
|
||||||
|
# Start classpath OPTIONS.
|
||||||
|
# These control what classes are on the classpath
|
||||||
|
# for a full listing do
|
||||||
|
# java -jar start.jar --list-options
|
||||||
|
#-----------------------------------------------------------
|
||||||
|
OPTIONS=Server,jsp,jmx,resources,websocket,ext,plus,annotations,keycloak
|
||||||
|
]]>
|
||||||
|
</programlisting>
|
||||||
|
|
||||||
|
</para>
|
||||||
|
</section>
|
||||||
|
|
||||||
|
<section>
|
||||||
|
<title>Required Per WAR Configuration</title>
|
||||||
|
<para>
|
||||||
|
Enabling Keycloak for your WARs is the same as the Jetty 9.x adapter. Our 8.1.x adapter supports both keycloak.json
|
||||||
|
and the jboss-web.xml advanced configuration. See <link linkend="jetty9_per_war">Required Per WAR Configuration</link>
|
||||||
|
</para>
|
||||||
|
</section>
|
||||||
|
</section>
|
|
@ -30,7 +30,7 @@ $ java -jar $JETTY_HOME/start.jar --add-to-startd=keycloak
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section>
|
<section id="jetty9_per_war">
|
||||||
<title>Required Per WAR Configuration</title>
|
<title>Required Per WAR Configuration</title>
|
||||||
<para>
|
<para>
|
||||||
This section describes how to secure a WAR directly by adding config and editing files within your WAR package.
|
This section describes how to secure a WAR directly by adding config and editing files within your WAR package.
|
||||||
|
|
Loading…
Reference in a new issue