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

Merge pull request #18 from jenmalloy/securing-apps_fix-RHSSO-633-take-2

Browse source 
fix version number issue
This commit is contained in:
Jen Malloy 2017-03-02 15:03:06 -05:00 committed by GitHub
commit afdc4bee54
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
securing_apps/book-product.json
View file

@ -12,10 +12,10 @@
"title": "Securing Applications and Services Guide", "title": "Securing Applications and Services Guide",
"project": { "project": {
"name": "Red Hat Single Sign-On", "name": "Red Hat Single Sign-On",
"version": "7.1.0", "version": "7.1",
"versionMvn": "2.4.0.Final-redhat-1", "versionMvn": "2.4.0.Final-redhat-1",
"doc_base_url": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/", "doc_base_url": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/",
"doc_info_version_url": "7.1-Beta" "doc_info_version_url": "7.1"
}, },
"community": false, "community": false,
"product": true, "product": true,

2
securing_apps/topics/oidc/java/client-authentication.adoc
View file

@ -22,7 +22,7 @@ This is based on the https://tools.ietf.org/html/rfc7523[RFC7523] specification.
* The client must have the private key and certificate. For {{book.project.name}} this is available through the traditional `keystore` file, which is either available on the client application's classpath or somewhere on the file system. * The client must have the private key and certificate. For {{book.project.name}} this is available through the traditional `keystore` file, which is either available on the client application's classpath or somewhere on the file system.
* Once the client application is started, it allows to download it's public key in https://self-issued.info/docs/draft-ietf-jose-json-web-key.html[JWKS] format using a URL such as \http://myhost.com/myapp/k_jwks, assuming that \http://myhost.com/myapp is the base URL of your client application. This URL can be used by {{book.project.name}} (see below). * Once the client application is started, it allows to download its public key in https://self-issued.info/docs/draft-ietf-jose-json-web-key.html[JWKS] format using a URL such as \http://myhost.com/myapp/k_jwks, assuming that \http://myhost.com/myapp is the base URL of your client application. This URL can be used by {{book.project.name}} (see below).
* During authentication, the client generates a JWT token and signs it with its private key and sends it to {{book.project.name}} in * During authentication, the client generates a JWT token and signs it with its private key and sends it to {{book.project.name}} in
the particular backchannel request (for example, code-to-token request) in the `client_assertion` parameter. the particular backchannel request (for example, code-to-token request) in the `client_assertion` parameter.

2
securing_apps/topics/oidc/java/fuse/install-feature.adoc
View file

@ -70,7 +70,7 @@ cd /path-to-fuse/jboss-fuse-6.3.0.redhat-198
unzip -q /path-to-adapter-zip/keycloak-fuse-adapter-dist-2.5.4.Final.zip unzip -q /path-to-adapter-zip/keycloak-fuse-adapter-dist-2.5.4.Final.zip
{% endif %} {% endif %}
{% if book.product %} {% if book.product %}
unzip -q /path-to-adapter-zip/rh-sso-{{book.project.version}}-fuse-adapter.zip unzip -q /path-to-adapter-zip/rh-sso-7.1.0-fuse-adapter.zip
{% endif %} {% endif %}
---- ----
. Start Fuse and run these commands in the fuse/karaf terminal: . Start Fuse and run these commands in the fuse/karaf terminal: