diff --git a/openidm-doc/src/main/asciidoc/connectors-guide/chap-ldap.adoc b/openidm-doc/src/main/asciidoc/connectors-guide/chap-ldap.adoc index 01d438599..c4763516f 100644 --- a/openidm-doc/src/main/asciidoc/connectors-guide/chap-ldap.adoc +++ b/openidm-doc/src/main/asciidoc/connectors-guide/chap-ldap.adoc @@ -191,7 +191,7 @@ Search filter that group entries must match. If `true`, OpenIDM modifies group membership when entries are renamed or deleted. + -In the sample LDAP connector configuration file provided with OpenIDM, this property is set to `false`. This means that LDAP group membership is not modified when entries are renamed or deleted in OpenIDM. To ensure that entries are removed from LDAP groups when the entries are deleted, set this property to `true` or enable referential integrity on the LDAP server. For information about configuring referential integrity in OpenDJ, see link:../../../opendj/3.5/server-dev-guide/#referential-integrity[Configuring Referential Integrity, window=\_top] in the __OpenDJ Administration Guide__. +In the sample LDAP connector configuration file provided with OpenIDM, this property is set to `false`. This means that LDAP group membership is not modified when entries are renamed or deleted in OpenIDM. To ensure that entries are removed from LDAP groups when the entries are deleted, set this property to `true` or enable referential integrity on the LDAP server. For information about configuring referential integrity in OpenDJ, see xref:opendj:server-dev-guide:chap-groups.adoc#referential-integrity[Configuring Referential Integrity] in the __OpenDJ Directory Server Developer's Guide__. `maintainPosixGroupMembership`:: If `true`, OpenIDM modifies POSIX group membership when entries are renamed or deleted. diff --git a/openidm-doc/src/main/asciidoc/connectors-guide/chap-sap.adoc b/openidm-doc/src/main/asciidoc/connectors-guide/chap-sap.adoc index 599a2e6dd..0bd7a3433 100644 --- a/openidm-doc/src/main/asciidoc/connectors-guide/chap-sap.adoc +++ b/openidm-doc/src/main/asciidoc/connectors-guide/chap-sap.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!: @@ -496,7 +496,7 @@ For optimum performance, set this value to an integer between `5` and `10`. -- -. To test this connector, you can use the sample Groovy scripts available on the link:hhttps://github.com/OpenIdentityPlatform/OpenICF/releases/[GitHub, window=\_blank]. You can find the source for these scripts in this location, in the `samples/` directory, as well as the `samples/r3/` subdirectory. +. To test this connector, you can use the sample Groovy scripts available on the link:https://github.com/OpenIdentityPlatform/OpenICF/releases/[GitHub, window=\_blank]. You can find the source for these scripts in this location, in the `samples/` directory, as well as the `samples/r3/` subdirectory. + [none] * `TestSAP.groovy` diff --git a/openidm-doc/src/main/asciidoc/getting-started/chap-where-to-go.adoc b/openidm-doc/src/main/asciidoc/getting-started/chap-where-to-go.adoc index 9a2f58ddf..28179c89f 100644 --- a/openidm-doc/src/main/asciidoc/getting-started/chap-where-to-go.adoc +++ b/openidm-doc/src/main/asciidoc/getting-started/chap-where-to-go.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!: @@ -89,7 +89,7 @@ OpenIDM includes support for connectors to the following external resources: * Salesforce (see xref:../connectors-guide/chap-salesforce.adoc#chap-salesforce["Salesforce Connector"] in the __Connectors Guide__). -* Any LDAPv3-compliant directory, including link:../../../opendj/install-guide[OpenDJ, window=\_blank] and Active Directory (see xref:../connectors-guide/chap-ldap.adoc#chap-ldap["Generic LDAP Connector"] in the __Connectors Guide__). +* Any LDAPv3-compliant directory, including xref:opendj:install-guide:index.adoc[OpenDJ] and Active Directory (see xref:../connectors-guide/chap-ldap.adoc#chap-ldap["Generic LDAP Connector"] in the __Connectors Guide__). * CSV Files (see xref:../connectors-guide/chap-csv.adoc#chap-csv["CSV File Connector"] in the __Connectors Guide__). diff --git a/openidm-doc/src/main/asciidoc/integrators-guide/appendix-scripting.adoc b/openidm-doc/src/main/asciidoc/integrators-guide/appendix-scripting.adoc index f64adea7c..25de5e651 100644 --- a/openidm-doc/src/main/asciidoc/integrators-guide/appendix-scripting.adoc +++ b/openidm-doc/src/main/asciidoc/integrators-guide/appendix-scripting.adoc @@ -1181,7 +1181,7 @@ The following tables list the available variables, based on each of these items. |=== |Object Type |Trigger |Variable -.6+a|managed object config object +.7+a|managed object config object a|onCreate, postCreate a|object, newObject diff --git a/openidm-doc/src/main/asciidoc/integrators-guide/chap-auth.adoc b/openidm-doc/src/main/asciidoc/integrators-guide/chap-auth.adoc index c67d7ec70..3cadb7d2d 100644 --- a/openidm-doc/src/main/asciidoc/integrators-guide/chap-auth.adoc +++ b/openidm-doc/src/main/asciidoc/integrators-guide/chap-auth.adoc @@ -465,7 +465,7 @@ The `OPENAM_SESSION` module enables you to protect an OpenIDM deployment with Op For detailed options, see xref:appendix-auth-modules.adoc#openam-module-details["OPENAM_SESSION Module Configuration Options"]. + -The use case is when you need to integrate IDM endpoints behind the scenes within other applications, such as with a company intranet portal. In that configuration, users would log into OpenAM to access the portal; at that point, their sessions would use the OpenAM SSO cookie, also known as `iPlanetDirectoryPro`. For more information, see the OpenAM Administration Guide section on link:../../../openam/13.5/admin-guide/#session-state-cookies[Session Cookies, window=\_blank]. +The use case is when you need to integrate IDM endpoints behind the scenes within other applications, such as with a company intranet portal. In that configuration, users would log into OpenAM to access the portal; at that point, their sessions would use the OpenAM SSO cookie, also known as `iPlanetDirectoryPro`. For more information, see the OpenAM Administration Guide section on xref:openam:admin-guide:chap-session-state.adoc#session-state-cookies[Session Cookies]. + [NOTE] diff --git a/openidm-doc/src/main/asciidoc/integrators-guide/chap-passwords.adoc b/openidm-doc/src/main/asciidoc/integrators-guide/chap-passwords.adoc index 61a1cd0e9..3eca0d5c6 100644 --- a/openidm-doc/src/main/asciidoc/integrators-guide/chap-passwords.adoc +++ b/openidm-doc/src/main/asciidoc/integrators-guide/chap-passwords.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!: @@ -376,7 +376,7 @@ The following sections describe how to use the password synchronization plugin f [#pwd-sync-opendj] ==== Synchronizing Passwords With OpenDJ -Password synchronization with OpenDJ requires communication over the secure LDAP protocol (LDAPS). If you have not set up OpenDJ for LDAPS, do this before you start, as described in the link:../../../opendj/3.5/admin-guide/configure-ssl[OpenDJ Administration Guide, window=\_blank]. +Password synchronization with OpenDJ requires communication over the secure LDAP protocol (LDAPS). If you have not set up OpenDJ for LDAPS, do this before you start, as described in xref:opendj:admin-guide:chap-connection-handlers.adoc#configure-ssl[LDAP Client Access Over SSL] in the __OpenDJ Administration Guide__. OpenIDM must be installed, and running before you continue with the procedures in this section. diff --git a/openidm-doc/src/main/asciidoc/integrators-guide/chap-synchronization.adoc b/openidm-doc/src/main/asciidoc/integrators-guide/chap-synchronization.adoc index acb7681cb..2824690d1 100644 --- a/openidm-doc/src/main/asciidoc/integrators-guide/chap-synchronization.adoc +++ b/openidm-doc/src/main/asciidoc/integrators-guide/chap-synchronization.adoc @@ -63,7 +63,7 @@ To perform this polling, liveSync relies on a change detection mechanism on the [NOTE] ====== -In the case of OpenDJ, the change log (`cn=changelog`) can be read only by `cn=directory manager` by default. If you are configuring liveSync with OpenDJ, the `principle` that is defined in the LDAP connector configuration must have access to the change log. For information about allowing a regular user to read the change log, see link:../../../opendj/3.5/admin-guide/#read-ecl-as-regular-user[To Allow a User to Read the Change Log, window=\_blank] in the __Administration Guide__ for OpenDJ. +In the case of OpenDJ, the change log (`cn=changelog`) can be read only by `cn=directory manager` by default. If you are configuring liveSync with OpenDJ, the `principle` that is defined in the LDAP connector configuration must have access to the change log. For information about allowing a regular user to read the change log, see xref:opendj:admin-guide:chap-replication.adoc#read-ecl-as-regular-user[To Allow a User to Read the Change Log] in the __Administration Guide__ for OpenDJ. ====== Implicit synchronization:: diff --git a/openidm-doc/src/main/asciidoc/samples-guide/chap-fullstack-sample.adoc b/openidm-doc/src/main/asciidoc/samples-guide/chap-fullstack-sample.adoc index 49a020251..51741120e 100644 --- a/openidm-doc/src/main/asciidoc/samples-guide/chap-fullstack-sample.adoc +++ b/openidm-doc/src/main/asciidoc/samples-guide/chap-fullstack-sample.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!: @@ -67,9 +67,9 @@ When you configure OpenAM, you need the following information to configure OpenD This sample assumes that you will configure OpenAM on a separate system from OpenIDM. -Install OpenAM as described in link:../../../openam/install-guide/#configure-openam-custom[To Custom Configure OpenAM, window=\_blank]. +Install OpenAM as described in xref:openam:install-guide:chap-install-core.adoc#configure-openam-custom[To Custom Configure OpenAM]. -During the installation process, include the parameters described in xref:#external-ldap-config-full-stack["External OpenDJ Configuration"]. Alternatively, if you already have an operational instance of OpenAM, set up an external instance of OpenDJ as described in link:../../../openam/13/admin-guide/#realm-data-store[To Configure a Data Store, window=\_blank]. +During the installation process, include the parameters described in xref:#external-ldap-config-full-stack["External OpenDJ Configuration"]. Alternatively, if you already have an operational instance of OpenAM, set up an external instance of OpenDJ as described in xref:openam:admin-guide:chap-realms.adoc#realm-data-store[To Configure a Data Store]. [#install-fullstack] @@ -127,7 +127,7 @@ image::images/openam-auth-basic.png[] + For detailed information on the options associated with the `OPENAM_SESSION` module, see xref:../integrators-guide/appendix-auth-modules.adoc#openam-module-details["OPENAM_SESSION Module Configuration Options"] in the __Integrator's Guide__. -* Select Advanced Properties to access additional options. Typically, you should only have to modify the `OpenAM Login URL` to match the Login URL of the OpenAM server. If you are working with the OpenAM Top-Level Realm, as described in link:../../../openam/13/admin-guide/#chap-realms[Configuring Realms, window=\_blank], and the given FQDN (`openam.example.com`), with an OpenAM web archive file of `openam.war` the following URL should work in this text box: `\https://openam.example.com:8443/openam/XUI/#login` +* Select Advanced Properties to access additional options. Typically, you should only have to modify the `OpenAM Login URL` to match the Login URL of the OpenAM server. If you are working with the OpenAM Top-Level Realm, as described in xref:openam:admin-guide:chap-realms.adoc[Configuring Realms], and the given FQDN (`openam.example.com`), with an OpenAM web archive file of `openam.war` the following URL should work in this text box: `\https://openam.example.com:8443/openam/XUI/#login` + image::images/openam-auth-adv.png[] diff --git a/openidm-doc/src/main/asciidoc/samples-guide/chap-groovy-samples.adoc b/openidm-doc/src/main/asciidoc/samples-guide/chap-groovy-samples.adoc index 8ea733d59..ed31b88db 100644 --- a/openidm-doc/src/main/asciidoc/samples-guide/chap-groovy-samples.adoc +++ b/openidm-doc/src/main/asciidoc/samples-guide/chap-groovy-samples.adoc @@ -171,10 +171,6 @@ To run this command, you must be in the `create-connector` directory, in which y ---- $ mvn install [INFO] Scanning for projects... -Downloading: http://maven.forgerock.org/repo/releases/org/forgerock/openicf/connectors/ - connectors-parent/1.5.0.0/connectors-parent-1.5.0.0.pom -Downloaded: http://maven.forgerock.org/repo/releases/org/forgerock/openicf/connectors/ - connectors-parent/1.5.0.0/connectors-parent-1.5.0.0.pom (21 KB at 9.2 KB/sec) [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building 1.4.1.0 diff --git a/openidm-doc/src/main/asciidoc/samples-guide/chap-ldap-samples.adoc b/openidm-doc/src/main/asciidoc/samples-guide/chap-ldap-samples.adoc index 8ff63ae27..10ee55108 100644 --- a/openidm-doc/src/main/asciidoc/samples-guide/chap-ldap-samples.adoc +++ b/openidm-doc/src/main/asciidoc/samples-guide/chap-ldap-samples.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!: @@ -1187,7 +1187,7 @@ The options shown in the associated configuration files can be easily modified t [#more-sample6-realad] ==== Sample 6 with an Active AD Deployment -If you have an existing, active instance of AD, set up OpenDJ, as described in the link:../../../opendj/install-guide[OpenDJ Installation Guide, window=\_blank]. +If you have an existing, active instance of AD, set up OpenDJ, as described in the xref:opendj:install-guide:index.adoc[OpenDJ Installation Guide]. During installation, populate OpenDJ with the data in the `Example.ldif` file, available in the `sample6/data` directory. diff --git a/openidm-doc/src/main/asciidoc/samples-guide/chap-workflow-samples.adoc b/openidm-doc/src/main/asciidoc/samples-guide/chap-workflow-samples.adoc index df6304c23..84ae24f21 100644 --- a/openidm-doc/src/main/asciidoc/samples-guide/chap-workflow-samples.adoc +++ b/openidm-doc/src/main/asciidoc/samples-guide/chap-workflow-samples.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!: @@ -254,7 +254,7 @@ Note that the `curl` commands in this section use the secure port for OpenIDM (8 This use case assumes an OpenDJ server and populates the managed user repository with users from OpenDJ. To set up the sample, install and configure OpenDJ, as follows: -. Download and install OpenDJ, as described in link:../../../opendj/install-guide/#gui-install[To Install OpenDJ Directory Server With the GUI, window=\_blank]. +. Download and install OpenDJ, as described in xref:opendj:install-guide:chap-install.adoc#gui-install[To Install OpenDJ Directory Server With the GUI]. + This sample assumes that OpenDJ is listening on port 1389, the standard LDAP port for users who cannot use privileged ports.