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

KEYCLOAK-9343 fixes in getting started guide

Browse source
This commit is contained in:
Matthew Helmke 2019-01-17 07:40:30 -06:00 committed by Stian Thorgersen
parent 89e557a4d4
commit 0f27a023f8
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
getting_started/topics/first-boot/distribution-files-product.adoc
View file

@ -3,22 +3,22 @@
Download the {project_name} Server:
* *rh-sso-{project_version}.GA.zip*
* *rh-sso-{project_version}.zip*
NOTE: This file can be downloaded from https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downloadType=distributions&product=core.service.rhsso[the Red Hat customer portal].
The *rh-sso-{project_version}.GA.zip* file is the server-only distribution. It contains only the scripts and binaries to run the {project_name} server.
The *rh-sso-{project_version}.zip* file is the server-only distribution. It contains only the scripts and binaries to run the {project_name} server.
Place the file in a directory you choose and use the `unzip` utility to unpack it, like this:
.Linux/Unix
[source,bash,subs=+attributes]
----
$ unzip rh-sso-{project_version}.GA.zip
$ jar xf rh-sso-{project_version}.zip
----
.Windows
[source,bash,subs=+attributes]
----
> unzip rh-sso-{project_version}.GA.zip
> unzip rh-sso-{project_version}.zip
----

2
getting_started/topics/secure-jboss-app/before.adoc
View file

@ -3,7 +3,7 @@
Before you can secure a Java servlet application, you must complete the installation of {project_name} and create the initial admin user as shown in <<_install-boot, Installing and Booting>>.
There is one caveat: Even though {appserver_name} is bundled with keycloak, you cannot use this as an application container. Instead, you must run a separate {appserver_name} instance on the same machine as the {project_name} server to run your Java servlet application. Run the {project_name} using a different port than the {appserver_name}, to avoid port conflicts.
There is one caveat: Even though {appserver_name} is bundled with {project_name}, you cannot use this as an application container. Instead, you must run a separate {appserver_name} instance on the same machine as the {project_name} server to run your Java servlet application. Run the {project_name} using a different port than the {appserver_name}, to avoid port conflicts.
To adjust the port used, change the value of the `jboss.socket.binding.port-offset` system property when starting the server from the command line. The value of this property is a number that will be added to the base value of every port opened by the {project_name} server.