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

Merge pull request #90 from jenmalloy/RHSSO-920

Browse source 
Fixed RHSSO-920
This commit is contained in:
Jen Malloy 2017-03-31 13:34:55 -04:00 committed by GitHub
commit 45e3761d8a
2 changed files with 6 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
authorization_services/topics/enforcer/js-adapter.adoc
View file

@ -7,7 +7,7 @@ This library is based on the {{book.project.name}} JavaScript adapter, which can
You can obtain this library from a running a {{book.project.name}} Server instance by including the following `script` tag in your web page:
```html
<script src="http://${KEYCLOAK_HOST}/auth/js/keycloak-authz.js"></script>
<script src="http://$.../auth/js/keycloak-authz.js"></script>
```
Once you do that, you can create a `KeycloakAuthorization` instance as follows:

15
authorization_services/topics/getting-started/overview.adoc
View file

@ -1,26 +1,21 @@
[[_getting_started_overview]]
== Getting Started
Before you can participate in this tutorial, you need to complete the installation of {{book.project.name}} and create the
initial admin user as shown in the link:{{book.gettingstarted.link}}[{{book.gettingstarted.name}}] tutorial.
There is one caveat to this. You have to run a separate {{book.appServer}} instance on the same machine as the
{{book.project.name}} server. This separate instance will run your Java Servlet application. Because of this you will
have to run the {{book.project.name}} under a different port so that there are no port conflicts when running on the
same machine. Use the `jboss.socket.binding.port-offset` system property on 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 {{book.project.name}} server.
Before you can use this tutorial, you need to complete the installation of {{book.project.name}} and create the initial admin user as shown in the link:{{book.gettingstarted.link}}[{{book.gettingstarted.name}}] tutorial.
There is one caveat to this. You have to run a separate {{book.appServer}} instance on the same machine as {{book.project.name}} Server. This separate instance will run your Java Servlet application. Because of this you will have to run the {{book.project.name}} under a different port so that there are no port conflicts when running on the same machine. Use the `jboss.socket.binding.port-offset` system property on the command line. The value of this property is a number that will be added to the base value of every port opened by {{book.project.name}} Server.
To boot the {{book.project.name}} server:
To boot {{book.project.name}} Server:
.Linux/Unix
[source]
----
$ ${KEYCLOAK_SERVER_DIR}/bin/standalone.sh -Djboss.socket.binding.port-offset=100
$ .../bin/standalone.sh -Djboss.socket.binding.port-offset=100
----
.Windows
[source]
----
> ${KEYCLOAK_SERVER_DIR}\bin\standalone.bat -Djboss.socket.binding.port-offset=100
> ...\bin\standalone.bat -Djboss.socket.binding.port-offset=100
----
For more details about how to install and configure a {{book.appServer}}, please follow the steps on the link:{{book.adapterguide.link}}[{{book.adapterguide.name}}] tutorial.