diff --git a/authorization_services/book-product.json b/authorization_services/book-product.json index 5832d96b97..99f09c8f62 100755 --- a/authorization_services/book-product.json +++ b/authorization_services/book-product.json @@ -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" } } } diff --git a/authorization_services/topics/getting-started/hello-world/deploy.adoc b/authorization_services/topics/getting-started/hello-world/deploy.adoc index 43267956c7..a4d8b09015 100644 --- a/authorization_services/topics/getting-started/hello-world/deploy.adoc +++ b/authorization_services/topics/getting-started/hello-world/deploy.adoc @@ -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 ---- diff --git a/authorization_services/topics/getting-started/overview.adoc b/authorization_services/topics/getting-started/overview.adoc index 00e7bb8e25..1d1f062d86 100644 --- a/authorization_services/topics/getting-started/overview.adoc +++ b/authorization_services/topics/getting-started/overview.adoc @@ -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. diff --git a/getting_started/book-product.json b/getting_started/book-product.json index 31072131e5..27f89ac65b 100755 --- a/getting_started/book-product.json +++ b/getting_started/book-product.json @@ -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" + } } } diff --git a/getting_started/topics/first-boot/initial-user.adoc b/getting_started/topics/first-boot/initial-user.adoc index 954b300115..771675a29f 100755 --- a/getting_started/topics/first-boot/initial-user.adoc +++ b/getting_started/topics/first-boot/initial-user.adoc @@ -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}}]. diff --git a/getting_started/topics/first-realm/account.adoc b/getting_started/topics/first-realm/account.adoc index b1d7bba5ca..ff127e0118 100755 --- a/getting_started/topics/first-realm/account.adoc +++ b/getting_started/topics/first-realm/account.adoc @@ -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}}]. diff --git a/securing_apps/book-product.json b/securing_apps/book-product.json index a81d9aba14..a366037184 100755 --- a/securing_apps/book-product.json +++ b/securing_apps/book-product.json @@ -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" } diff --git a/securing_apps/topics/client-registration.adoc b/securing_apps/topics/client-registration.adoc index 7d9d9dcdd6..a96d5fb358 100644 --- a/securing_apps/topics/client-registration.adoc +++ b/securing_apps/topics/client-registration.adoc @@ -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 diff --git a/securing_apps/topics/oidc/java/client-authentication.adoc b/securing_apps/topics/oidc/java/client-authentication.adoc index ddcc2eebdd..a3a2a82406 100644 --- a/securing_apps/topics/oidc/java/client-authentication.adoc +++ b/securing_apps/topics/oidc/java/client-authentication.adoc @@ -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 %} diff --git a/securing_apps/topics/oidc/java/params_forwarding.adoc b/securing_apps/topics/oidc/java/params_forwarding.adoc index 99e692478f..665446cc08 100644 --- a/securing_apps/topics/oidc/java/params_forwarding.adoc +++ b/securing_apps/topics/oidc/java/params_forwarding.adoc @@ -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}}]. diff --git a/server_admin/book-product.json b/server_admin/book-product.json index 696caf3c75..a61ed5d531 100644 --- a/server_admin/book-product.json +++ b/server_admin/book-product.json @@ -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/" } } } diff --git a/server_admin/topics/MigrationFromOlderVersions.adoc b/server_admin/topics/MigrationFromOlderVersions.adoc index f3df466de5..0cf718f090 100644 --- a/server_admin/topics/MigrationFromOlderVersions.adoc +++ b/server_admin/topics/MigrationFromOlderVersions.adoc @@ -75,7 +75,7 @@ tags under the keycloak subsystem. Before migration, your keycloak subsystem sh ---- -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 diff --git a/server_admin/topics/account.adoc b/server_admin/topics/account.adoc index a9be4719f3..0c5f082838 100644 --- a/server_admin/topics/account.adoc +++ b/server_admin/topics/account.adoc @@ -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. diff --git a/server_admin/topics/authentication/password-policies.adoc b/server_admin/topics/authentication/password-policies.adoc index 941057e517..e83fd2a0d8 100644 --- a/server_admin/topics/authentication/password-policies.adoc +++ b/server_admin/topics/authentication/password-policies.adoc @@ -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 %} diff --git a/server_admin/topics/clients/client-oidc.adoc b/server_admin/topics/clients/client-oidc.adoc index 0e0ed44de2..48e581b432 100644 --- a/server_admin/topics/clients/client-oidc.adoc +++ b/server_admin/topics/clients/client-oidc.adoc @@ -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 <> diff --git a/server_admin/topics/clients/protocol-mappers.adoc b/server_admin/topics/clients/protocol-mappers.adoc index ff29c9d47e..b0c609567f 100644 --- a/server_admin/topics/clients/protocol-mappers.adoc +++ b/server_admin/topics/clients/protocol-mappers.adoc @@ -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 diff --git a/server_admin/topics/events/login.adoc b/server_admin/topics/events/login.adoc index af440286c5..b71438aa2d 100644 --- a/server_admin/topics/events/login.adoc +++ b/server_admin/topics/events/login.adoc @@ -104,5 +104,5 @@ that comes with your distribution and adding for example: ---- -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. diff --git a/server_admin/topics/identity-broker/first-login-flow.adoc b/server_admin/topics/identity-broker/first-login-flow.adoc index cba7875683..820ff23eb6 100644 --- a/server_admin/topics/identity-broker/first-login-flow.adoc +++ b/server_admin/topics/identity-broker/first-login-flow.adoc @@ -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 diff --git a/server_admin/topics/initialization.adoc b/server_admin/topics/initialization.adoc index 3ce0d2eb3b..5761257b79 100644 --- a/server_admin/topics/initialization.adoc +++ b/server_admin/topics/initialization.adoc @@ -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 diff --git a/server_admin/topics/login-settings/forgot-password.adoc b/server_admin/topics/login-settings/forgot-password.adoc index 2710117073..01fd5360c1 100644 --- a/server_admin/topics/login-settings/forgot-password.adoc +++ b/server_admin/topics/login-settings/forgot-password.adoc @@ -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 diff --git a/server_admin/topics/realms/themes.adoc b/server_admin/topics/realms/themes.adoc index 359d76c94e..a1cad1662d 100644 --- a/server_admin/topics/realms/themes.adoc +++ b/server_admin/topics/realms/themes.adoc @@ -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. diff --git a/server_admin/topics/roles/realm-roles.adoc b/server_admin/topics/roles/realm-roles.adoc index 3f53ca078f..19dfab6802 100644 --- a/server_admin/topics/roles/realm-roles.adoc +++ b/server_admin/topics/roles/realm-roles.adoc @@ -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. diff --git a/server_admin/topics/user-federation/ldap.adoc b/server_admin/topics/user-federation/ldap.adoc index 0fdbf3ade3..ce9d936aef 100644 --- a/server_admin/topics/user-federation/ldap.adoc +++ b/server_admin/topics/user-federation/ldap.adoc @@ -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). diff --git a/server_admin/topics/users/recaptcha.adoc b/server_admin/topics/users/recaptcha.adoc index 3c95b0541a..68ad7cad66 100755 --- a/server_admin/topics/users/recaptcha.adoc +++ b/server_admin/topics/users/recaptcha.adoc @@ -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. diff --git a/server_admin/topics/users/required-actions.adoc b/server_admin/topics/users/required-actions.adoc index 6128b317ba..de126c6579 100644 --- a/server_admin/topics/users/required-actions.adoc +++ b/server_admin/topics/users/required-actions.adoc @@ -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. diff --git a/server_admin/topics/users/user-registration.adoc b/server_admin/topics/users/user-registration.adoc index cf6b463749..2a0f2b636c 100644 --- a/server_admin/topics/users/user-registration.adoc +++ b/server_admin/topics/users/user-registration.adoc @@ -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. diff --git a/server_development/book-product.json b/server_development/book-product.json index d5dffb9997..ee8bc6fcb4 100755 --- a/server_development/book-product.json +++ b/server_development/book-product.json @@ -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" } } } diff --git a/server_installation/book-product.json b/server_installation/book-product.json index 58be605b80..993d8ce0eb 100755 --- a/server_installation/book-product.json +++ b/server_installation/book-product.json @@ -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/" } } } diff --git a/server_installation/topics/operating-mode/standalone-ha.adoc b/server_installation/topics/operating-mode/standalone-ha.adoc index 0636e70ddb..dbcb7b96de 100755 --- a/server_installation/topics/operating-mode/standalone-ha.adoc +++ b/server_installation/topics/operating-mode/standalone-ha.adoc @@ -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