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

edits based on review

Browse source
This commit is contained in:
Matthew Helmke 2018-12-11 10:27:44 -06:00 committed by Bruno Oliveira da Silva
parent c156bd151a
commit 5c5bf4f2a8
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
server_installation/topics/network/https.adoc
View file

@ -119,7 +119,7 @@ $ keytool -import -alias yourdomain -keystore keycloak.jks -file your-certificat
===== Configure {project_name} to Use the Keystore
Now that you have a Java keystore with the appropriate certificates, you need to configure your {project_name} installation to use it.
First, you must move the keystore file to the _configuration/_ directory of your deployment and edit the _standalone.xml_, _standalone-ha.xml_, or _host.xml_ file to use the keystore and enable HTTPS. (See <<_operating-mode, operating mode>>).
First, you must edit the _standalone.xml_, _standalone-ha.xml_, or _host.xml_ file to use the keystore and enable HTTPS. You may then either move the keystore file to the _configuration/_ directory of your deployment or the file in a location you choose and provide an absolute path to it. If you are using absolute paths, remove the optional `relative-to` parameter from your configuration (See <<_operating-mode, operating mode>>).
Add the new `security-realm` element using the CLI: