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

Update book-product.json files to fix links and book titles, plus assorted other fixes.

Browse source
This commit is contained in:
Sande Gilda 2017-03-01 16:19:29 -05:00
parent 7f67cf624d
commit 1084460648
31 changed files with 84 additions and 70 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

38
authorization_services/book-product.json
View file

@ -14,7 +14,11 @@
"product": true,
"images": "rhsso-images",
"appServer": "JBoss EAP 7",
"quickstartRepo": "https://github.com/redhat-developer/redhat-sso-quickstarts",
"quickstartRepo": {
"name": "Quickstarts for the Red Hat Single Sign-On (SSO) Server",
"dir": "redhat-sso-quickstarts",
"link": "https://github.com/redhat-developer/redhat-sso-quickstarts"
},
"project": {
"name": "Red Hat Single Sign-On",
"version": "7.1.0",
@ -22,23 +26,21 @@
"doc_base_url": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/",
"doc_info_version_url": "7.1"
},
"external_link": {
"keycloakjsadapter": {
"name": "JavaScript OpenID Connect Adapter",
"link": "/single/securing-applications-and-services-guide#javascript_adapter"
},
"keycloakgettingstarted": {
"name": "Getting Started",
"link": "/paged/getting-started-guide/"
},
"keycloakinstallingandboot": {
"name": "Installing and Boot",
"link": "/single/getting-started-guide/#install-boot"
},
"keycloakinstallclientadapter": {
"name": "Installing the Client Adapter",
"link": "/single/getting-started-guide/#installing_the_client_adapter"
}
"keycloakjsadapter": {
"name": "JavaScript OpenID Connect Adapter",
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/securing-applications-and-services-guide#javascript_adapter"
},
"keycloakgettingstarted": {
"name": "Getting Started",
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html/getting-started-guide/"
},
"keycloakinstallingandboot": {
"name": "Installing and Boot",
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/getting-started-guide/#install-boot"
},
"keycloakinstallclientadapter": {
"name": "Installing the Client Adapter",
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/getting-started-guide/#installing_the_client_adapter"
}
}
}

1
authorization_services/topics/getting-started/hello-world/deploy.adoc
View file

@ -20,6 +20,7 @@ $ git clone {{book.quickstartRepo.link}}
The application we are about to build and deploy is located at
[source, subs="attributes"]
----
$ cd {{book.quickstartRepo.dir}}/app-authz-jee-vanilla
----

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

@ -2,7 +2,7 @@
== 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.
initial admin user as shown in the link:{{book.keycloakgettingstarted.link}}[{{book.keycloakgettingstarted.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
@ -23,7 +23,7 @@ $ ${KEYCLOAK_SERVER_DIR}/bin/standalone.sh -Djboss.socket.binding.port-offset=10
> ${KEYCLOAK_SERVER_DIR}\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.
For more details about how to install and configure a {{book.appServer}}, please follow the steps on the link:{{book.keycloakinstallclientadapter.link}}[{{book.keycloakinstallclientadapter.name}}] tutorial.
After installing and booting both servers you should be able to access {{book.project.name}} Admin Console at http://localhost:8180/auth/admin/ and also the {{book.appServer}} instance at
http://localhost:8080.

13
getting_started/book-product.json
View file

@ -22,15 +22,22 @@
"installguide": {
"name": "Server Installation and Configuration Guide",
"link": "/single/server-installation-and-configuration-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/server-installation-and-configuration-guide/"
},
"adminguide": {
"name": "Server Administration Guide",
"link": "/single/server-administration-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/server-administration-guide/"
},
"clientadapter": "RH-SSO-{{book.project.version}}-eap7-adapter.zip",
"appServer": "JBoss EAP 7",
"quickstartRepo": "https://github.com/redhat-developer/redhat-sso-quickstarts"
"appserver": {
"name": "JBoss EAP 7"
},
"quickstartRepo": {
"name": "Quickstarts for the Red Hat Single Sign-On (SSO) Server",
"dir": "redhat-sso-quickstarts",
"link": "https://github.com/redhat-developer/redhat-sso-quickstarts"
}
}
}

2
getting_started/topics/first-boot/initial-user.adoc
View file

@ -12,6 +12,6 @@ you can start creating realms and users and registering applications to be secur
NOTE: You can only create an initial admin user on the Welcome Page if you connect using `localhost`. This is a security
precaution. You can also create the initial admin user at the command line with the `add-user-keycloak.sh` script. For more details see
link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.installguide.link}}[{{book.installguide.name}}] and link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.adminguide.link}}[{{book.adminguide.name}}].
link:{{book.installguide.link}}[{{book.installguide.name}}] and link:{{book.adminguide.link}}[{{book.adminguide.name}}].

2
getting_started/topics/first-realm/account.adoc
View file

@ -14,7 +14,7 @@ User Account Link::
image:../../{{book.images}}/update-password.png[]
The User Account Service page opens. Every user in a realm has access to this Account Service by default.
You can update profile information and change or add additional credentials. For more information on this service see the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.adminguide.link}}[{{book.adminguide.name}}].
You can update profile information and change or add additional credentials. For more information on this service see the link:{{book.adminguide.link}}[{{book.adminguide.name}}].

2
securing_apps/book-product.json
View file

@ -22,7 +22,7 @@
"images": "rhsso-images",
"adminguide": {
"name": "Server Administration Guide",
"link": "/single/server-administration-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/server-administration-guide/"
},
"fuseVersion": "JBoss Fuse 6.3.0 Rollup 1"
}

4
securing_apps/topics/client-registration.adoc
View file

@ -24,13 +24,13 @@ There is an alternative to register new client without any token as well, but th
==== Bearer Token
The bearer token can be issued on behalf of a user or a Service Account. The following permissions are required to invoke the endpoints (see link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.adminguide.link}}[{{book.adminguide.name}}] for more details):
The bearer token can be issued on behalf of a user or a Service Account. The following permissions are required to invoke the endpoints (see link:{{book.adminguide.link}}[{{book.adminguide.name}}] for more details):
* create-client or manage-client - To create clients
* view-client or manage-client - To view clients
* manage-client - To update or delete client
If you are using a bearer token to create clients it's recommend to use a token from a Service Account with only the `create-client` role (see link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.adminguide.link}}[{{book.adminguide.name}}] for more details).
If you are using a bearer token to create clients it's recommend to use a token from a Service Account with only the `create-client` role (see link:{{book.adminguide.link}}[{{book.adminguide.name}}] for more details).
==== Initial Access Token

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

@ -32,7 +32,7 @@ Then you can choose to either:
** Configure the JWKS URL where {{book.project.name}} can download the client's public keys. This can be a URL such as \http://myhost.com/myapp/k_jwks (see details above). This option is the most flexible, since the client can rotate its keys anytime and {{book.project.name}} then always downloads new keys when needed without needing to change the configuration. More accurately, {{book.project.name}} downloads new keys when it sees the token signed by an unknown `kid` (Key ID).
** Upload the client's public key or certificate, either in PEM format, in JWK format, or from the keystore. With this option, the public key is hardcoded and must be changed when the client generates a new key pair.
You can even generate your own keystore from the {{book.project.name}} admininstration console if you don't have your own available.
For more details on how to set up the {{book.project.name}} administration console see {{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.adminguide.link}}[{{book.adminguide.name}}].
For more details on how to set up the {{book.project.name}} administration console see {{book.adminguide.link}}[{{book.adminguide.name}}].
For set up on the adapter side you need to have something like this in your `keycloak.json` file:
@ -59,7 +59,7 @@ For inspiration, you can take a look at the examples distribution into the main
===== Add Your Own Client Authentication Method
You can add your own client authentication method as well. You will need to implement both client-side and server-side providers. For more details see the `Authentication SPI` section in {{book.developerguide.link}}[{{book.developerguide.name}}].
You can add your own client authentication method as well. You will need to implement both client-side and server-side providers. For more details see the `Authentication SPI` section in link:{{book.developerguide.link}}[{{book.developerguide.name}}].
{% endif %}

2
securing_apps/topics/oidc/java/params_forwarding.adoc
View file

@ -29,4 +29,4 @@ The supported parameters are:
Most of the parameters are described in the http://openid.net/specs/openid-connect-core-1_0.html#AuthorizationEndpoint[OIDC specification].
The only exception is parameter `kc_idp_hint`, which is specific to {{book.project.name}} and contains the name of the identity provider to automatically use.
For more information see the `Identity Brokering` section in {{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.adminguide.link}}[{{book.adminguide.name}}].
For more information see the `Identity Brokering` section in link:{{book.adminguide.link}}[{{book.adminguide.name}}].

6
server_admin/book-product.json
View file

@ -22,16 +22,16 @@
"developerguide": {
"name": "Server Developer Guide",
"link": "/single/server-developer-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/server-developer-guide/"
},
"installguide": {
"name": "Server Installation and Configuration Guide",
"link": "/single/server-installation-and-configuration-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/server-installation-and-configuration-guide/"
},
"adapterguide": {
"name": "Securing Applications and Services Guide",
"link": "/single/securing-applications-and-services-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/securing-applications-and-services-guide/"
}
}
}

2
server_admin/topics/MigrationFromOlderVersions.adoc
View file

@ -75,7 +75,7 @@ tags under the keycloak subsystem. Before migration, your keycloak subsystem sh
</subsystem>
----
The jboss-cli tool is discussed in detail in link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.installguide.link}}[{{book.installguide.name}}].
The jboss-cli tool is discussed in detail in link:{{book.installguide.link}}[{{book.installguide.name}}].
==== migrate-json in Standalone Mode

4
server_admin/topics/account.adoc
View file

@ -9,7 +9,7 @@ change their credentials, update their profile, and view their login sessions.
image:../{{book.images}}/account-service-profile.png[]
The initial page is the user's profile, which is the `Account` left menu item. This is where they specify basic data about themselves. This screen can be extended
to allow the user to manage additional attributes. See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}] for more details.
to allow the user to manage additional attributes. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}] for more details.
The `Password` left menu item allows the user to change their password.
@ -42,4 +42,4 @@ image:../{{book.images}}/account-service-apps.png[]
=== Themeable
Like all UIs in {{book.project.name}}, the User Account Service is completely themeable and internationalizable.
See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}] for more details.
See the link:{{book.developerguide.link}}[{{book.developerguide.name}}] for more details.

2
server_admin/topics/authentication/password-policies.adoc
View file

@ -30,7 +30,7 @@ Here's an explanation of each policy type:
{% if book.community %}
HashAlgorithm::
Passwords are not stored as clear text. Instead they are hashed using standard hashing algorithms before they are stored or validated.
The only built-in and default algorithm available is PBKDF2. See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}]
The only built-in and default algorithm available is PBKDF2. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}]
on how to plug in your own algorithm. Note that if you do change the algorithm, password hashes will not change in storage until
the next time the user logs in.
{% endif %}

6
server_admin/topics/clients/client-oidc.adoc
View file

@ -36,7 +36,7 @@ This specifies an alpha-numeric string that will be used as the client identifie
*Name*
This is the display name for the client whenever it is displayed in a {{book.project.name}} UI screen. You can localize
the value of this field by setting up a replacement string value i.e. $\{myapp}. See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}]
the value of this field by setting up a replacement string value i.e. $\{myapp}. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}]
for more information.
*Description*
@ -104,7 +104,7 @@ If this is on, clients are allowed to use the OIDC <<fake/../../sso-protocols/oi
For {{book.project.name}} specific client adapters, this is the callback endpoint for the client. The {{book.project.name}}
server will use this URI to make callbacks like pushing revocation policies, performing backchannel logout, and other
administrative operations. For {{book.project.name}} servlet adapters, this can be the root URL of the servlet application.
For more information see link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.adapterguide.link}}[{{book.adapterguide.name}}].
For more information see link:{{book.adapterguide.link}}[{{book.adapterguide.name}}].
*Web Origins*
@ -118,7 +118,7 @@ This protocol exists to protect against XSS, CSRF and other JavaScript-based att
`Web Origins` setting for the client are embedded within the access token sent to the client application. The client
application can then use this information to decide whether or not to allow a CORS request to be invoked on it. This is
an extension to the OIDC protocol so only {{book.project.name}} client adapters support this feature.
See link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.adapterguide.link}}[{{book.adapterguide.name}}] for more information.
See link:{{book.adapterguide.link}}[{{book.adapterguide.name}}] for more information.
To fill in the `Web Origins` data, enter in a base URL and click the + sign to add. Click the - sign next to URLs you want to remove.
Remember that you still have to click the `Save` button!

2
server_admin/topics/clients/client-saml.adoc
View file

@ -37,7 +37,7 @@ Client ID::
Name::
This is the display name for the client whenever it is displayed in a {{book.project.name}} UI screen. You can localize
the value of this field by setting up a replacement string value i.e. $\{myapp}. See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}]
the value of this field by setting up a replacement string value i.e. $\{myapp}. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}]
for more information.
Description::

2
server_admin/topics/clients/oidc/confidential.adoc
View file

@ -43,7 +43,7 @@ client publishes it's public key in https://self-issued.info/docs/draft-ietf-jos
client changes it's keys, {{book.project.name}} will automatically download them without need to re-import anything on {{book.project.name}} side.
If you use client secured by {{book.project.name}} adapter, you can configure the JWKS URL like https://myhost.com/myapp/k_jwks assuming that https://myhost.com/myapp is the
root URL of your client application. See {{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}] for additional details.
root URL of your client application. See link:{{book.developerguide.link}}[{{book.developerguide.name}}] for additional details.
WARNING: For the performance purposes, {{book.project.name}} caches the public keys of the OIDC clients. If you think that private key of your client
was compromised, it is obviously good to update your keys, but it's also good to clear the keys cache. See <<fake/../../realms/cache.adoc#_clear-cache, Clearing the cache>>

2
server_admin/topics/clients/protocol-mappers.adoc
View file

@ -34,7 +34,7 @@ Consent Required::
Consent Text::
If your client requires consent and the `Consent` switch is on, this is the text that will be displayed by the user.
The value for this text is localizable by specifying a substitution variable with `$\{var-name}` strings. The
localized value is then configured within property files in your theme. See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}]
localized value is then configured within property files in your theme. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}]
for more information on localization.
Most OIDC mappers also allow you to control where the claim gets put. You can opt to include or exclude the claim from both the

2
server_admin/topics/events/login.adoc
View file

@ -104,5 +104,5 @@ that comes with your distribution and adding for example:
</spi>
----
See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.installguide.link}}[{{book.installguide.name}}] for more details on
See the link:{{book.installguide.link}}[{{book.installguide.name}}] for more details on
where the `standalone.xml`, `standalone-ha.xml`, or `domain.xml` file lives.

2
server_admin/topics/identity-broker/first-login-flow.adoc
View file

@ -24,7 +24,7 @@ You can re-configure the existing flow. (For example you can disable some authen
{% if project.community %}
You can also create a new authentication flow and/or write your own Authenticator implementations and use it in your flow.
See link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}] for more details.
See link:{{book.developerguide.link}}[{{book.developerguide.name}}] for more details.
{% endif %}
==== Default First Login Flow

2
server_admin/topics/initialization.adoc
View file

@ -1,7 +1,7 @@
== Server Initialization
After performing all the installation and configuration tasks defined in the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.installguide.link}}[{{book.installguide.name}}],
After performing all the installation and configuration tasks defined in the link:{{book.installguide.link}}[{{book.installguide.name}}],
you will need to create an initial admin account.
{{book.project.name}} does not have any configured admin account out of the box.
This account will allow you to create an admin that can log into the _master_ realm's administration console so that

2
server_admin/topics/login-settings/forgot-password.adoc
View file

@ -19,7 +19,7 @@ to a page where they can enter in their username or email and receive an email w
image:../../{{book.images}}/forgot-password-page.png[]
The text sent in the email is completely configurable. You just need to extend or edit the theme associated with it.
See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}] for more information.
See the link:{{book.developerguide.link}}[{{book.developerguide.name}}] for more information.
When the user clicks on the email link, they will be asked to update their password, and, if they have an OTP generator
set up, they will also be asked to reconfigure this as well. Depending on the security requirements of your organization

4
server_admin/topics/realms/themes.adoc
View file

@ -21,12 +21,12 @@ Email Theme::
The link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}] goes into how to create a new themes or modify existing ones.
The link:{{book.developerguide.link}}[{{book.developerguide.name}}] goes into how to create a new themes or modify existing ones.
==== Internationalization
Every UI screen is internationalized in {{book.project.name}}. The default language is English, but if you turn on the
`Internationalization` switch on the `Theme` tab you can choose which locales you want to support and what the default locale
will be. The next time a user logs in, they will be able to choose a language on the login page to use for the login screens,
User Account Management UI, and Admin Console. The link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}] explains
User Account Management UI, and Admin Console. The link:{{book.developerguide.link}}[{{book.developerguide.name}}] explains
how you can offer additional languages.

2
server_admin/topics/roles/realm-roles.adoc
View file

@ -13,7 +13,7 @@ and hit the `Save` button.
image:../../{{book.images}}/role.png[]
The value for the `description` field is localizable by specifying a substitution variable with `$\{var-name}` strings.
The localized value is then configured within property files in your theme. See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}]
The localized value is then configured within property files in your theme. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}]
for more information on localization. If a client requires user _consent_, this description string will be displayed on the
consent page for the user.

2
server_admin/topics/user-federation/ldap.adoc
View file

@ -56,7 +56,7 @@ When you configure a secured connection URL to your LDAP store(for example `ldap
{{book.project.name}} will use SSL for the communication with LDAP server.
The important thing is to properly configure a truststore on the {{book.project.name}} server side, otherwise {{book.project.name}} can't trust the SSL connection to LDAP.
The global truststore for the {{book.project.name}} can be configured with the Truststore SPI. Please check out the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.installguide.link}}[{{book.installguide.name}}] for more detail.
The global truststore for the {{book.project.name}} can be configured with the Truststore SPI. Please check out the link:{{book.installguide.link}}[{{book.installguide.name}}] for more detail.
If you don't configure the truststore SPI, the truststore will fallback to the default mechanism provided by Java (either the file provided by system property `javax.net.ssl.trustStore`
or the cacerts file from the JDK if the system property is not set).

2
server_admin/topics/users/recaptcha.adoc
View file

@ -33,5 +33,5 @@ values of both the `X-Frame-Options` and `Content-Security-Policy` headers.
image:../../{{book.images}}/security-headers.png[]
Once you do this, reCAPTCHA should show up on your registration page. You may want to edit _register.ftl_ in your login
theme to muck around with the placement and styling of the reCAPTCHA button. See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}]
theme to muck around with the placement and styling of the reCAPTCHA button. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}]
for more information on extending and creating themes.

2
server_admin/topics/users/required-actions.adoc
View file

@ -39,5 +39,5 @@ Simply click the checkbox in the `Default Action` column of the required actions
Many organizations have a requirement that when a new user logs in for the first time, they need to agree to the terms and conditions
of the website. {{book.project.name}} has this functionality implemented as a required action, but it requires some configuration. For one, you
have to go to the `Required Actions` tab described earlier and enable the `Terms and Conditions` action. You must also edit the
_terms.ftl_ file in the _base_ login theme. See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}] for more information on extending and
_terms.ftl_ file in the _base_ login theme. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}] for more information on extending and
creating themes.

2
server_admin/topics/users/user-registration.adoc
View file

@ -22,6 +22,6 @@ and a new password.
image:../../{{book.images}}/registration-form.png[]
You can change the look and feel of the registration form as well as removing or adding additional fields that must be entered.
See the link:{{book.project.doc_base_url}}{{book.project.doc_info_version_url}}{{book.developerguide.link}}[{{book.developerguide.name}}] for more information.
See the link:{{book.developerguide.link}}[{{book.developerguide.name}}] for more information.

12
server_development/book-product.json
View file

@ -21,20 +21,24 @@
"images": "rhsso-images",
"adminguide": {
"name": "Server Administration Guide",
"link": "/single/server-administration-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/server-administration-guide/"
},
"clientguide": {
"name": "Securing Applications and Services Guide",
"link": "/single/securing-applications-and-services-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/securing-applications-and-services-guide/"
},
"installguide": {
"name": "Server Installation and Configuration Guide",
"link": "/single/server-installation-and-configuration-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/server-installation-and-configuration-guide/"
},
"apidocs": {
"name": "API Documentation",
"link": "/single/api-documentation/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/api-documentation/"
},
"adapterguide": {
"name": "JavaScript OpenID Connect Adapter",
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/securing-applications-and-services-guide#javascript_adapter"
}
}
}

20
server_installation/book-product.json
View file

@ -24,44 +24,44 @@
"version": "7.0",
"admindoc": {
"name": "JBoss EAP Configuration Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/configuration-guide/configuration-guide"
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/html-single/configuration-guide/configuration-guide"
},
"datasource": {
"name": "JBoss EAP Configuration Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/configuration-guide/#datasource_management"
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/html-single/configuration-guide/#datasource_management"
},
"network": {
"name": "JBoss EAP Configuration Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/configuration-guide/#network_and_port_configuration"
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/html-single/configuration-guide/#network_and_port_configuration"
},
"socket": {
"name": "JBoss EAP Configuration Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/configuration-guide/#network_and_port_configuration"
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/html-single/configuration-guide/#network_and_port_configuration"
},
"loadbalancer": {
"name": "JBoss EAP Configuration Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/configuration-guide/#configuring_high_availability"
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/html-single/configuration-guide/#configuring_high_availability"
},
"jgroups": {
"name": "JBoss EAP Configuration Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/configuration-guide/#cluster_communication_jgroups"
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/html-single/configuration-guide/#cluster_communication_jgroups"
},
"caching": {
"name": "JBoss EAP Configuration Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/configuration-guide/#infinispan"
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/html-single/configuration-guide/#infinispan"
},
"jpa": {
"name": "JBoss EAP Development Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/development-guide/#hibernate"
"link": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/html-single/development-guide/#hibernate"
}
},
"developerguide": {
"name": "Server Developer Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-Beta/server-developer-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-Beta/html-single/server-developer-guide/"
},
"adminguide": {
"name": "Server Administration Guide",
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-Beta/server-administration-guide/"
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-Beta/html-single/server-administration-guide/"
}
}
}

2
server_installation/topics/operating-mode/standalone-ha.adoc
View file

@ -22,7 +22,7 @@ image:../../{{book.images}}/standalone-ha-config-file.png[]
WARNING: Any changes you make to this file while the server is running will not take effect and may even be overwritten
by the server. Instead use the the command line scripting or the web console of {{book.appserver.name}}. See
the link:{{book.appserver.admindoc.link}}[{{_book.appserver.admindoc.name}}_] for more information.
the link:{{book.appserver.admindoc.link}}[_{{book.appserver.admindoc.name}}_] for more information.
==== Standalone Clustered Boot Script