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

Inclusion of add user instructions for overlay

Browse source
This commit is contained in:
Bruno Oliveira 2016-03-02 10:14:41 -03:00
parent cc776abacb
commit b8c50c431c
1 changed files with 11 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docbook/auth-server-docs/reference/en/en-US/modules/server-installation.xml
View file

@ -128,7 +128,13 @@ bin/add-user.[sh|bat] -r master -u <username> -p <password>
]]></programlisting>
Then restart the server.
</para>
</section>
<para>
For <literal>keycloak-overlay</literal>, please make sure to use:
<programlisting><![CDATA[
bin/add-user-keycloak.[sh|bat] -r master -u <username> -p <password>
]]></programlisting>
</para>
</section>
<section>
<title>Relational Database Configuration</title>
@ -832,7 +838,7 @@ $ keytool -import -alias yourdomain -keystore keycloak.jks -file your-certificat
<link linkend='themes'>Themes</link> sections for more information on how to do this.
</para>
</section>
<section>
<title>Installing Keycloak Server as Root Context</title>
<para>
@ -855,11 +861,11 @@ $ keytool -import -alias yourdomain -keystore keycloak.jks -file your-certificat
<note>
If you have run your server before altering the root context, your database
will contain references to the old /auth context. Your clients may also have incorrect
references. To fix this on the server side, you will need to <link linkend="export-import">export
your database to json, make corrections, and then import.</link> Client-side keycloak.json
references. To fix this on the server side, you will need to <link linkend="export-import">export
your database to json, make corrections, and then import.</link> Client-side keycloak.json
files will need to be updated manually as well.
</note>
</para>
</section>
</chapter>