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

fixing RHSSO622 623 624 625 pulled in 613

Browse source
This commit is contained in:
Chuck Copello 2016-11-29 17:15:51 -05:00
parent 5fddcd91c6
commit a42274f893
3 changed files with 6 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
topics/oidc/java/java-adapter-config.adoc
View file

@ -38,7 +38,7 @@ This is what one might look like:
----
You can use `${...}` enclosure for system property replacement. For example `${jboss.server.config.dir}` would be replaced by `/path/to/{{book.project.name}}`.
Replacement of environment variables is also supported via the `env` prefix, e.g. `${env.MY_ENVIRONMENT_VARIABLE}`.
Replacement of environment variables is also supported via the `env` prefix, e.g. `${env.MY_ENVIRONMENT_VARIABLE}`.
The initial config file can be obtained from the the admin console. This can be done by opening the admin console, select `Clients` from the menu and clicking
on the corresponding client. Once the page for the client is opened click on the `Installation` tab and select `Keycloak OIDC JSON`.
@ -118,6 +118,7 @@ expose-token::
The default value is _false_.
credentials::
Not required for public clients or where the client is "bearer-only."
Specify the credentials of the application. This is an object notation where the key is the credential type and the value is the value of the credential type.
Currently `password` and `jwt` is supported.
This is _REQUIRED_.
@ -148,7 +149,7 @@ truststore::
Client making HTTPS requests need a way to verify the host of the server they are talking to.
This is what the trustore does.
The keystore contains one or more trusted host certificates or certificate authorities.
You can create this truststore by extracting the public certificate of the {{book.project.name}} server's SSL keystore.
You can create this truststore by extracting the public certificate of the {{book.project.name}} server's SSL keystore.
This is _REQUIRED_ unless `ssl-required` is `none` or `disable-trust-manager` is `true`.
truststore-password::

4
topics/overview/supported-platforms.adoc
View file

@ -27,7 +27,7 @@
===== Node.js (server-side)
* <<fake/../../oidc/nodejs-adapter.adoc#_nodejs_adapter,Node.js>>
===== Apache Cordova
===== JavaScript
* <<fake/../../oidc/javascript-adapter.adoc#_javascript_adapter,JavaScript>>
{% if book.community %}
@ -76,4 +76,4 @@
===== Apache HTTP Server
* https://github.com/UNINETT/mod_auth_mellon[mod_auth_mellon]
* <<fake/../../saml/mod-auth-mellon.adoc#,mod_auth_mellon>>

4
topics/saml/java/jboss-adapter.adoc
View file

@ -15,6 +15,4 @@ To be able to secure WAR apps deployed on JBoss EAP, you must install and config
{% endif %}
You then provide a keycloak config, `/WEB-INF/keycloak-saml.xml` file in your WAR and change the auth-method to KEYCLOAK-SAML within web.xml.
Both methods are described in this section.
Both methods are described in this section.