From b8c50c431cf3eda9925c27478cc66b341515f629 Mon Sep 17 00:00:00 2001 From: Bruno Oliveira Date: Wed, 2 Mar 2016 10:14:41 -0300 Subject: [PATCH] Inclusion of add user instructions for overlay --- .../en/en-US/modules/server-installation.xml | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/docbook/auth-server-docs/reference/en/en-US/modules/server-installation.xml b/docbook/auth-server-docs/reference/en/en-US/modules/server-installation.xml index aceff9ba96..6ab7b5aaad 100755 --- a/docbook/auth-server-docs/reference/en/en-US/modules/server-installation.xml +++ b/docbook/auth-server-docs/reference/en/en-US/modules/server-installation.xml @@ -128,7 +128,13 @@ bin/add-user.[sh|bat] -r master -u -p ]]> Then restart the server. - + + For keycloak-overlay, please make sure to use: + -p +]]> + +
Relational Database Configuration @@ -832,7 +838,7 @@ $ keytool -import -alias yourdomain -keystore keycloak.jks -file your-certificat Themes sections for more information on how to do this.
- +
Installing Keycloak Server as Root Context @@ -855,11 +861,11 @@ $ keytool -import -alias yourdomain -keystore keycloak.jks -file your-certificat 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 export - your database to json, make corrections, and then import. Client-side keycloak.json + references. To fix this on the server side, you will need to export + your database to json, make corrections, and then import. Client-side keycloak.json files will need to be updated manually as well. - +