From f23b8d08ced34bcd3709b7203db3d10abc11c63e Mon Sep 17 00:00:00 2001 From: Valera V Harseko Date: Thu, 1 Oct 2026 00:00:53 +0300 Subject: [PATCH] [#1155] Fix typos, unresolved placeholders and dead ForgeRock links in the guides - Fix the hhttps typo in the mobile samples link - Enable attribute substitution in the three console blocks that showed {openam-version} literally - Close the unterminated example block in Getting Started, which swallowed the "Trying It Out" section - Drop the stray bold markers around the self-service email examples and keep them as literals - Replace or remove the links to backstage.forgerock.com and forgerock.org, which no longer serve this content Fixes #1155 --- .../asciidoc/admin-guide/chap-auth-services.adoc | 7 ++----- .../main/asciidoc/admin-guide/chap-mobile.adoc | 4 ++-- .../admin-guide/chap-usr-selfservices.adoc | 16 +++++----------- .../main/asciidoc/dev-guide/chap-client-dev.adoc | 2 +- .../asciidoc/dev-guide/chap-customizing.adoc | 8 ++++---- .../main/asciidoc/dev-guide/chap-fedlets.adoc | 4 ---- .../src/main/asciidoc/dev-guide/chap-sts.adoc | 4 ++-- .../getting-started/chap-first-steps.adoc | 4 +++- .../main/asciidoc/install-guide/chap-cts.adoc | 4 +--- .../install-guide/chap-install-tools.adoc | 10 ++-------- .../install-guide/chap-prepare-install.adoc | 2 +- .../main/asciidoc/reference/chap-config-ref.adoc | 5 ++--- .../main/asciidoc/reference/chap-endpoints.adoc | 6 +++--- .../upgrade-guide/chap-legacy-servers.adoc | 4 ++-- 14 files changed, 30 insertions(+), 50 deletions(-) diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-auth-services.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-auth-services.adoc index 9b925b72e6..7b6c9b40fe 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-auth-services.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-auth-services.adoc @@ -12,7 +12,7 @@ information: "Portions copyright [year] [name of copyright owner]". Copyright 2017 ForgeRock AS. - Portions Copyright 2024-2025 3A Systems LLC. + Portions Copyright 2024-2026 3A Systems LLC. //// :figure-caption!: @@ -2051,7 +2051,7 @@ One-time passwords are valid for five minutes after they are generated by defaul [NOTE] ====== -You may also also need to configure the login page session timeouts in OpenAM. For more information, see link:https://backstage.forgerock.com/knowledge/kb/article/a23597700[How do I configure login page session timeouts in OpenAM (All versions)?, window=\_blank] +You may also need to configure the login page session timeouts in OpenAM. ====== + `ssoadm` attribute: `sunAMAuthHOTPPasswordValidityDuration` @@ -4430,9 +4430,6 @@ For detailed information about the available properties, see xref:../reference/c Push Notification Service:: Configures how OpenAM sends push notifications to registered devices, including endpoints, and access credentials. -+ -For information on provisioning the credentials required by the Push Notification Service, see link:https://backstage.forgerock.com/knowledge/kb/article/a47604373[How do I set up AM/OpenAM Push Notification Service credentials, window=\_blank] in the __ForgeRock Knowledge Base__. - + For detailed information about the available properties, see xref:../reference/chap-config-ref.adoc#push-notification-service-configuration["Push Notification Service"] in the __Reference__. diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-mobile.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-mobile.adoc index f846d7c2cc..312982cb7c 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-mobile.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-mobile.adoc @@ -12,7 +12,7 @@ information: "Portions copyright [year] [name of copyright owner]". Copyright 2017 ForgeRock AS. - Portions Copyright 2024-2025 3A Systems LLC. + Portions Copyright 2024-2026 3A Systems LLC. //// :figure-caption!: @@ -107,7 +107,7 @@ Furthermore, OpenAM REST APIs are built on an underlying common REST framework d [#get-mobile-sample-apps] === Getting Source Code for Sample Mobile Applications -Source code for the sample mobile applications is available in sample repositories on the link:hhttps://github.com/OpenIdentityPlatform/[GitHub, window=\_blank]. Get local clones of one or more of the following repositories so that you can try these sample applications on your system: +Source code for the sample mobile applications is available in sample repositories on the link:https://github.com/OpenIdentityPlatform/[GitHub, window=\_blank]. Get local clones of one or more of the following repositories so that you can try these sample applications on your system: * link:https://github.com/OpenIdentityPlatform/mobile-samples-android-openam-apps[OpenAM OAuth2.0 Android sample app, window=\_blank] diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-usr-selfservices.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-usr-selfservices.adoc index ee50fc4c4a..84d2ab38c3 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-usr-selfservices.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-usr-selfservices.adoc @@ -276,16 +276,13 @@ Default: 900 seconds. .. In the Outgoing Email Subject field, enter the Subject line of your email in the New Value field, and then click Add. + -The subject line format is `lang|subject-text`, where `lang` is the ISO-639 language code, such as `en` for English, `fr` for French, and others. For example, the subject line values could be: *`en|Registration Email` -* and *`fr|Inscription E-mail` -*. +The subject line format is `lang|subject-text`, where `lang` is the ISO-639 language code, such as `en` for English, `fr` for French, and others. For example, the subject line values could be: `en|Registration Email` and `fr|Inscription E-mail`. .. In the Outgoing Email Body field, enter the text of your email in the New Value field, and then click Add. + The email body text format is `lang|email-text`, where `lang` is the ISO-639 language code. Note that email body text must be all on one line and can contain any HTML tags within the body of the text. + -For example, the email body text could be: *`en|Thank you for registration to our site! Click here to register to the site.` -* +For example, the email body text could be: `+en|Thank you for registration to our site! Click here to register to the site.+` . In the Valid Creation Attributes field, enter the user attributes the user can set during the user self-registration. The attributes are based on the OpenAM identity repository. @@ -337,15 +334,13 @@ Default: 900 seconds. .. In the Outgoing Email Subject field, enter the subject line of your email in the New Value field, and then click Add. + -The subject line format is `lang|subject-text`, where `lang` is the ISO-639 language code, such as `en` for English, `fr` for French, and others. For example, the subject line value could be: *`en|Forgotten Password Email` -*. +The subject line format is `lang|subject-text`, where `lang` is the ISO-639 language code, such as `en` for English, `fr` for French, and others. For example, the subject line value could be: `en|Forgotten Password Email`. .. In the Outgoing Email Body field, enter the text of your email in the New Value field, and then click Add. + The email body text format is `lang|email-text`, where `lang` is the ISO-639 language code. Note that email body text must be all on one line and can contain any HTML tags within the body of the text. + -For example, the email body text could be: *`en|Thank you for request! Click here to reset your password.` -* +For example, the email body text could be: `+en|Thank you for request! Click here to reset your password.+` . Under Advanced Configuration, change the default Forgotten Password Confirmation Email URL for your deployment. The default is: `\http://openam.example.com:8080/openam/XUI/#passwordReset/`. @@ -385,8 +380,7 @@ Default: 900 seconds. .. In the Outgoing Email Subject field, enter the subject line of your email in the New Value field, and then click Add. + -The subject Line format is `lang|subject-text`, where `lang` is the ISO 639 language code, such as `en` for English, `fr` for French, and others. For example, the subject line value could be: *`en|Forgotten username email` -*. +The subject Line format is `lang|subject-text`, where `lang` is the ISO 639 language code, such as `en` for English, `fr` for French, and others. For example, the subject line value could be: `en|Forgotten username email`. .. In the Outgoing Email Body field, enter the text of your email in the New Value field, and then click Add. + diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-client-dev.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-client-dev.adoc index f858f073fa..df7cf10223 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-client-dev.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-client-dev.adoc @@ -9055,7 +9055,7 @@ The sample web application deploys in your container to show you the client SDK . Deploy the .war in your Java web application container such as Apache Tomcat or JBoss. + -[source, console] +[source, console, subs="attributes+"] ---- $ cp ExampleClientSDK-WAR-{openam-version}.war /path/to/tomcat/webapps/client.war ---- diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-customizing.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-customizing.adoc index 8c97b1689b..d71e76b2a8 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-customizing.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-customizing.adoc @@ -499,7 +499,7 @@ This section shows how to customize authentication with a sample custom authenti The sample authentication module prompts for a user name and password to authenticate the user, and handles error conditions. The sample shows how you integrate an authentication module into OpenAM such that you can configure the module through OpenAM console, and also localize the user interface. -For information on downloading and building OpenAM sample source code, see link:https://backstage.forgerock.com/knowledge/kb/article/a47487197[How do I access and build the sample code provided for OpenAM 12.x, 13.x and AM (All versions)?, window=\_blank] in the __Knowledge Base__. +The OpenAM sample source code is in the link:https://github.com/OpenIdentityPlatform/OpenAM/tree/master/openam-samples[openam-samples, window=\_blank] directory of the OpenAM source code on GitHub. -- Get a local clone so that you can try the sample on your system. In the sources, you find the following files under the `/path/to/openam-source/openam-samples/custom-authentication-module` directory: @@ -1068,7 +1068,7 @@ Build the module with Apache Maven, and install the module in OpenAM. After you successfully build the module, you find the `.jar` file in the `target/` directory of the project. -For information on downloading and building OpenAM sample source code, see link:https://backstage.forgerock.com/knowledge/kb/article/a47487197[How do I access and build the sample code provided for OpenAM 12.x, 13.x and AM (All versions)?, window=\_blank] in the __Knowledge Base__. +The OpenAM sample source code is in the link:https://github.com/OpenIdentityPlatform/OpenAM/tree/master/openam-samples[openam-samples, window=\_blank] directory of the OpenAM source code on GitHub. [#installing-sample-auth-module] @@ -1363,7 +1363,7 @@ This section shows how to build and use a custom policy plugin that implements a The OpenAM policy framework lets you build plugins that extend subject conditions, environment conditions, and resource attributes. -For information on downloading and building OpenAM sample source code, see link:https://backstage.forgerock.com/knowledge/kb/article/a47487197[How do I access and build the sample code provided for OpenAM 12.x, 13.x and AM (All versions)?, window=\_blank] in the __Knowledge Base__. +The OpenAM sample source code is in the link:https://github.com/OpenIdentityPlatform/OpenAM/tree/master/openam-samples[openam-samples, window=\_blank] directory of the OpenAM source code on GitHub. Get a local clone so that you can try the sample on your system. In the sources, you find the following files under the `/path/to/openam-source/openam-samples/policy-evaluation-plugin` directory: -- @@ -1412,7 +1412,7 @@ Follow the steps in this procedure to build the sample plugin: . If you have not already done so, download and build the samples. + -For information on downloading and building OpenAM sample source code, see link:https://backstage.forgerock.com/knowledge/kb/article/a47487197[How do I access and build the sample code provided for OpenAM 12.x, 13.x and AM (All versions)?, window=\_blank] in the __Knowledge Base__. +The OpenAM sample source code is in the link:https://github.com/OpenIdentityPlatform/OpenAM/tree/master/openam-samples[openam-samples, window=\_blank] directory of the OpenAM source code on GitHub. . Check out the `master` branch of the OpenAM source. diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-fedlets.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-fedlets.adoc index f43265cdc2..eff2563041 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-fedlets.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-fedlets.adoc @@ -1287,10 +1287,6 @@ The following settings define settings for access to certificates and private ke Other sections in this guide explain how to configure a Fedlet for signing and encryption including how to work with the keystores that these settings reference, and how to specify public key certificates in standard SAML v2.0 metadata. When working with a Java Fedlet, see the section on xref:#fedlet-signing-encryption["Enabling Signing and Encryption in a Fedlet"]. -[TIP] -====== -Although this section focuses on Java Fedlets, if you are working with a .NET Fedlet see link:https://backstage.forgerock.com/knowledge/kb/article/a99870342[How do I use Fedlets in .NET applications in OpenAM (All versions)?, window=\_blank] in the __ForgeRock Knowledge Base__. -====== `com.sun.identity.saml.xmlsig.keystore`:: This sets the path to the keystore file that holds public key certificates of IDPs and key pairs for the Fedlet. diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-sts.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-sts.adoc index 7e9163c89e..c0e01b10eb 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-sts.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/dev-guide/chap-sts.adoc @@ -46,11 +46,11 @@ Several sections in this chapter reference STS code examples. The following proc . If you have not already done so, download and build the STS samples. + -For information on downloading and building OpenAM sample source code, see link:https://backstage.forgerock.com/knowledge/kb/article/a47487197[How do I access and build the sample code provided for OpenAM 12.x, 13.x and AM (All versions)?, window=\_blank] in the __Knowledge Base__. +The OpenAM sample source code is in the link:https://github.com/OpenIdentityPlatform/OpenAM/tree/master/openam-samples[openam-samples, window=\_blank] directory of the OpenAM source code on GitHub. . Check out the `master` branch of the OpenAM source. + -You can find the STS code examples under `/path/to/openam-samples-external/sts-example-code`. +You can find the STS code examples under `/path/to/openam-source/openam-samples/sts-example-code`. ==== diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/getting-started/chap-first-steps.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/getting-started/chap-first-steps.adoc index 877ea52755..06f99475bc 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/getting-started/chap-first-steps.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/getting-started/chap-first-steps.adoc @@ -12,7 +12,7 @@ information: "Portions copyright [year] [name of copyright owner]". Copyright 2017 ForgeRock AS. - Portions Copyright 2024-2025 3A Systems LLC. + Portions Copyright 2024-2026 3A Systems LLC. //// :figure-caption!: @@ -323,6 +323,8 @@ Run the image: docker run -it --name apache_agent -p 8000:80 -h www.example.com --shm-size 2G --network openam-quickstart apache_agent ---- +==== + [#try-it-out] === Trying It Out diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-cts.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-cts.adoc index 3af44fa123..cc7e6c2516 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-cts.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-cts.adoc @@ -12,7 +12,7 @@ information: "Portions copyright [year] [name of copyright owner]". Copyright 2017 ForgeRock AS. - Portions Copyright 2024-2025 3A Systems LLC. + Portions Copyright 2024-2026 3A Systems LLC. //// :figure-caption!: @@ -53,8 +53,6 @@ Active/passive deployments are slightly simpler to deploy. Active/passive deploy + Affinity deployments allow you to spread requests to the CTS token store across multiple directory master instances. Affinity deployments are a good fit for deployments with many OpenAM servers. + -For more information on CTS affinity deployments, see link:https://backstage.forgerock.com/knowledge/kb/article/a94140799[Best practice for using Core Token Service (CTS) Affinity based load balancing in AM (All versions) and OpenAM 13.5.1, window=\_top] in the __ForgeRock Knowledge Base__. -+ Do not deploy CTS token stores behind a load balancer. Instead, specify connections to the directory server instances that comprise the CTS token store by using the Connection String(s) property in the CTS configuration. + diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-install-tools.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-install-tools.adoc index 528f8d6b00..d235309622 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-install-tools.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-install-tools.adoc @@ -67,7 +67,7 @@ $ mkdir -p /path/to/openam-tools/admin . Unpack the tools: + -[source, console] +[source, console, subs="attributes+"] ---- $ cd /path/to/openam-tools/admin $ unzip ~/Downloads/openam/SSOAdminTools-{openam-version}.zip @@ -149,12 +149,6 @@ $ tail -2 /path/to/openam-tools/admin/openam/bin/ssoadm -D"javax.net.ssl.trustStore=/path/to/tomcat/conf/keystore.jks" \ com.sun.identity.cli.CommandManager "$@" ---- -+ - -[NOTE] -====== -In non-production environments, you can configure the `ssoadm` command to trust all server certificates. For more information, see link:https://backstage.forgerock.com/knowledge/kb/book/b88592244#trust[Q. How do I configure ssoadm to trust all certificates?, window=\_top] in the __ForgeRock Knowledge Base__. -====== . (Optional) If you use IBM Java, add `-D"amCryptoDescriptor.provider=IBMJCE"` and `-D"amKeyGenDescriptor.provider=IBMJCE"` options to the `ssoadm` or `ssoadm.bat` script before using the script. + @@ -306,7 +300,7 @@ DS_DIRMGRPASSWD=password When the OpenAM server `.war` file is deployed and running, you can configure it by using the tool with the properties file. + -[source, console] +[source, console, subs="attributes+"] ---- $ java -jar openam-configurator-tool-{openam-version}.jar --file config.properties Checking license acceptance...License terms accepted. diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-prepare-install.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-prepare-install.adoc index 0e378fb4a7..6a0d87df4d 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-prepare-install.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-prepare-install.adoc @@ -1118,7 +1118,7 @@ $ ./ldapsearch --hostname openam.example.com --port 1389 --bindDN "cn=Directory . Repeat these steps for all appropriate OpenDJ instances. ==== -For additional information, see link:https://backstage.forgerock.com/knowledge/kb/article/a97304600[How do I prevent anonymous access in DS/OpenDJ (All version), window=\_blank] in the __ForgeRock Knowledge Base__. +For additional information, see link:https://doc.openidentityplatform.org/opendj/admin-guide/chap-privileges-acis#access-control-disable-anonymous[ACI: Disable Anonymous Access, window=\_blank] in the OpenDJ __Administration Guide__. diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/reference/chap-config-ref.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/reference/chap-config-ref.adoc index 7270569126..f593a0b8f7 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/reference/chap-config-ref.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/reference/chap-config-ref.adoc @@ -3297,7 +3297,6 @@ Use the ForgeRock Backstage website to provision values for the following Simple * SNS Client Region -For information on provisioning the credentials required by the Push Notification Service, see link:https://backstage.forgerock.com/knowledge/kb/article/a47604373[How do I set up AM/OpenAM Push Notification Service credentials, window=\_blank] in the __BackStage Help Knowledge Base__. -- `ssoadm` service name: `PushNotificationService` @@ -4330,7 +4329,7 @@ Outgoing Email Body:: Customizes the user self-registration email body text. + -Default: `en|

Click on this link to register.

` +Default: `+en|

Click on this link to register.

+` + `ssoadm` attribute: `selfServiceUserRegistrationEmailBody` @@ -4455,7 +4454,7 @@ Outgoing Email Body:: Customizes the forgotten password email body text. + -Default: `en|

Click on this link to reset your password.

` +Default: `+en|

Click on this link to reset your password.

+` + `ssoadm` attribute: `selfServiceForgottenPasswordEmailBody` diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/reference/chap-endpoints.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/reference/chap-endpoints.adoc index f7594dd62b..57a186d88b 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/reference/chap-endpoints.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/reference/chap-endpoints.adoc @@ -974,7 +974,7 @@ Accessible as an option to the Discovery Service for a specific user. To edit an [#console-web-services-jsp-endpoints] === Web Services Console JSP Endpoints -Web services include endpoints in the `console/webservices` subdirectory. You can use them to define legacy options for services, such as the Liberty Identity Federation Framework (ID-FF). As such, these endpoints may be less essential to your implementation of OpenAM. For more information, see the link:http://www.forgerock.org/security_advisory2.html[OpenAM Wiki on Web Services, window=\_blank]. +Web services include endpoints in the `console/webservices` subdirectory. You can use them to define legacy options for services, such as the Liberty Identity Federation Framework (ID-FF). As such, these endpoints may be less essential to your implementation of OpenAM. -- `WSAuthNServices.jsp`:: @@ -1038,7 +1038,7 @@ This simple endpoint includes a redirection of the ServiceURI, and specifies Ope This endpoint is called with the `PWResetInvalidURLViewBean` class, when a module servlet gets an invalid URL. `PWResetQuestion.jsp`:: -Starts the password reset process by prompting for the User ID. For more information on the process, see the method for the associated `PWResetQuestionModel`, available from the link:http://download.forgerock.org/downloads/openam/javadocs/internal/com/sun/identity/password/ui/model/PWResetQuestionModel.html[Interface PWResetQuestionModel specification page, window=\_blank]. +Starts the password reset process by prompting for the User ID. For more information on the process, see the methods of the associated `com.sun.identity.password.ui.model.PWResetQuestionModel` interface. `PWResetSuccess.jsp`:: Specifies the endpoint that is called when an account password is successfully reset. @@ -1236,7 +1236,7 @@ Used with the servlet named `GatewayServlet`. Associated with the `Gateway.java` The associated `.java` file is associated with session failover. `/sessionservice, /profileservice, /policyservice, /namingservice, /loggingservice, /authservice, /notificationservice`:: -All of these endpoints are associated with link:http://www.forgerock.org/security_advisory1.html[OpenAM Security Advisory #201203, window=\_blank]. As suggested in the advisory, if you are using OpenAM version 9.5.4 or 10.0.0, you should be sure to apply the updates required to upgrade your systems to versions 9.5.5 or 10.0.1 (or higher). +All of these endpoints are associated with OpenAM Security Advisory #201203. As suggested in the advisory, if you are using OpenAM version 9.5.4 or 10.0.0, you should be sure to apply the updates required to upgrade your systems to versions 9.5.5 or 10.0.1 (or higher). `/jaxrpc/*, /identityservices/*`:: These endpoints provide information on configured web services, including the port name, status, URL, and implementation class. Both endpoints show the same data. The IdentityServices servlet name points to the following description: "Web Service Endpoint - Identity Services". diff --git a/openam-documentation/openam-doc-source/src/main/asciidoc/upgrade-guide/chap-legacy-servers.adoc b/openam-documentation/openam-doc-source/src/main/asciidoc/upgrade-guide/chap-legacy-servers.adoc index 50bfc0c05c..f6e6b5f56c 100644 --- a/openam-documentation/openam-doc-source/src/main/asciidoc/upgrade-guide/chap-legacy-servers.adoc +++ b/openam-documentation/openam-doc-source/src/main/asciidoc/upgrade-guide/chap-legacy-servers.adoc @@ -12,7 +12,7 @@ information: "Portions copyright [year] [name of copyright owner]". Copyright 2017 ForgeRock AS. - Portions Copyright 2024 3A Systems LLC. + Portions Copyright 2024-2026 3A Systems LLC. //// :figure-caption!: @@ -23,7 +23,7 @@ [#chap-legacy-servers] == Migrating Legacy Servers -Rather than upgrade legacy servers (running OpenSSO or Sun Access Manager, or an link:https://backstage.forgerock.com/#!/knowledge/kb/article/a18529200[OpenAM version that is no longer supported, window=\_blank]), you instead manually migrate from your existing deployment to a new deployment. +Rather than upgrade legacy servers (running OpenSSO or Sun Access Manager, or an OpenAM version that is no longer supported), you instead manually migrate from your existing deployment to a new deployment. For complex legacy deployments, Open Identity Platform Community link:https://github.com/OpenIdentityPlatform/.github/wiki/Approved-Vendor-List[Approved Vendors, window=\_blank] can assist you in the migration process.