From f347eb9a64a07ad240eb28486704009ff23faa85 Mon Sep 17 00:00:00 2001 From: Karuna Vengurlekar Date: Thu, 6 Aug 2026 16:03:08 +0530 Subject: [PATCH 1/4] Add 2.2.1 updates --- .../marketplace/platform-supported-content/modules/ldap.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/en/docs/marketplace/platform-supported-content/modules/ldap.md b/content/en/docs/marketplace/platform-supported-content/modules/ldap.md index 4444f0e7930..82023c62f3e 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/ldap.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/ldap.md @@ -90,6 +90,10 @@ Starting from version 2.2.0, the module uses `objectGUID` as the primary identif If an LDAP group is deleted or renamed, any existing role mappings based on the original group name become invalid, which may result in users temporarily losing their assigned roles. To restore role assignments, update the mappings in the **LDAP group mapping** configuration and perform a resynchronization to reapply the appropriate roles. For more information, see the [Configuration](#configuration) section below. {{% /alert %}} +{{% alert color="warning" %}} +When upgrading from LDAP v2.2.0 to v2.2.1, duplicate LDAP Group records may exist if they were created in LDAP v2.2.0. After upgrading to version 2.2.1, run the `Ldap.MF_DeleteDuplicateGroups` migration microflow to detect and remove duplicate LDAP Group records. Once the cleanup is complete, run the [LDAP synchronization](/appstore/modules/ldap/#regular-synchronization) again. Add a unique constraint on the `ObjectGUID` attribute of the LDAP Group entity. The next LDAP release will include this unique constraint by default. +{{% /alert %}} + ## Configuration{#configuration} ### Regular Synchronization From 8813df042e2a8ae59bf2d9bcb168cec5eb003929 Mon Sep 17 00:00:00 2001 From: Karuna Vengurlekar Date: Tue, 11 Aug 2026 18:03:05 +0530 Subject: [PATCH 2/4] Add small changes --- .../docs/marketplace/platform-supported-content/modules/ldap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/marketplace/platform-supported-content/modules/ldap.md b/content/en/docs/marketplace/platform-supported-content/modules/ldap.md index 82023c62f3e..e62dadad0d8 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/ldap.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/ldap.md @@ -91,7 +91,7 @@ If an LDAP group is deleted or renamed, any existing role mappings based on the {{% /alert %}} {{% alert color="warning" %}} -When upgrading from LDAP v2.2.0 to v2.2.1, duplicate LDAP Group records may exist if they were created in LDAP v2.2.0. After upgrading to version 2.2.1, run the `Ldap.MF_DeleteDuplicateGroups` migration microflow to detect and remove duplicate LDAP Group records. Once the cleanup is complete, run the [LDAP synchronization](/appstore/modules/ldap/#regular-synchronization) again. Add a unique constraint on the `ObjectGUID` attribute of the LDAP Group entity. The next LDAP release will include this unique constraint by default. +When upgrading from LDAP v2.2.0 to v2.2.1, duplicate LDAP Group records may exist if they were created in LDAP v2.2.0. After upgrading to version 2.2.1, remove the unique constraint on the `ObjectGUID` attribute of the LDAP Group entity. Run the `Ldap.MF_DeleteDuplicateGroups` migration microflow to detect and remove duplicate LDAP Group records. Once the cleanup is complete, add a unique constraint on the `ObjectGUID` attribute of the LDAP Group entity and run the [LDAP synchronization](/appstore/modules/ldap/#regular-synchronization) again. {{% /alert %}} ## Configuration{#configuration} From b91f1a3073b8da5133161982391b0be6cd122933 Mon Sep 17 00:00:00 2001 From: Karuna Vengurlekar Date: Wed, 12 Aug 2026 17:43:48 +0530 Subject: [PATCH 3/4] Add - Refresh Groups --- .../marketplace/platform-supported-content/modules/ldap.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/marketplace/platform-supported-content/modules/ldap.md b/content/en/docs/marketplace/platform-supported-content/modules/ldap.md index e62dadad0d8..38d8c64380e 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/ldap.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/ldap.md @@ -87,11 +87,11 @@ The following instructions assume that you want the Administrator role in your a {{% alert color="info" %}} Starting from version 2.2.0, the module uses `objectGUID` as the primary identifier for users and groups. When you upgrade from an earlier version, the module matches existing records by name and assigns them the `objectGUID`. If the module cannot find a matching record, it creates a new record. This may result in duplicate records if your legacy data contains inconsistencies. After `objectGUID` is assigned, the module synchronizes Active Directory changes (including name changes) without creating duplicates. -If an LDAP group is deleted or renamed, any existing role mappings based on the original group name become invalid, which may result in users temporarily losing their assigned roles. To restore role assignments, update the mappings in the **LDAP group mapping** configuration and perform a resynchronization to reapply the appropriate roles. For more information, see the [Configuration](#configuration) section below. +If an LDAP group is deleted or renamed, any existing role mappings based on the original group name become invalid, which may result in users temporarily losing their assigned roles. To restore role assignments, update the mappings in the **LDAP group mapping** configuration, **Refresh** groups, and perform a resynchronization to reapply the appropriate roles. For more information, see the [Configuration](#configuration) section below. {{% /alert %}} {{% alert color="warning" %}} -When upgrading from LDAP v2.2.0 to v2.2.1, duplicate LDAP Group records may exist if they were created in LDAP v2.2.0. After upgrading to version 2.2.1, remove the unique constraint on the `ObjectGUID` attribute of the LDAP Group entity. Run the `Ldap.MF_DeleteDuplicateGroups` migration microflow to detect and remove duplicate LDAP Group records. Once the cleanup is complete, add a unique constraint on the `ObjectGUID` attribute of the LDAP Group entity and run the [LDAP synchronization](/appstore/modules/ldap/#regular-synchronization) again. +When upgrading from LDAP v2.2.0 to v2.2.1, duplicate LDAP Group records may exist if they were created in LDAP v2.2.0. After upgrading to version 2.2.1, remove the unique constraint on the `ObjectGUID` attribute of the LDAP Group entity. Run the `Ldap.MF_DeleteDuplicateGroups` migration microflow to detect and remove duplicate LDAP Group records. Once the cleanup is complete, add a unique constraint on the `ObjectGUID` attribute of the LDAP Group entity and **Refresh** groups. Run the [LDAP synchronization](/appstore/modules/ldap/#regular-synchronization) again. {{% /alert %}} ## Configuration{#configuration} From 88dd2a893f60eaf9593c20ef3768abf3eaee1afd Mon Sep 17 00:00:00 2001 From: Karuna Vengurlekar Date: Thu, 13 Aug 2026 10:54:09 +0530 Subject: [PATCH 4/4] Incorporate feedback --- .../docs/marketplace/platform-supported-content/modules/ldap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/marketplace/platform-supported-content/modules/ldap.md b/content/en/docs/marketplace/platform-supported-content/modules/ldap.md index 38d8c64380e..216fa4cd16b 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/ldap.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/ldap.md @@ -91,7 +91,7 @@ If an LDAP group is deleted or renamed, any existing role mappings based on the {{% /alert %}} {{% alert color="warning" %}} -When upgrading from LDAP v2.2.0 to v2.2.1, duplicate LDAP Group records may exist if they were created in LDAP v2.2.0. After upgrading to version 2.2.1, remove the unique constraint on the `ObjectGUID` attribute of the LDAP Group entity. Run the `Ldap.MF_DeleteDuplicateGroups` migration microflow to detect and remove duplicate LDAP Group records. Once the cleanup is complete, add a unique constraint on the `ObjectGUID` attribute of the LDAP Group entity and **Refresh** groups. Run the [LDAP synchronization](/appstore/modules/ldap/#regular-synchronization) again. +Version 2.2.0 of the LDAP module may have created duplicate LDAP Group records. After upgrading to 2.2.1, you can remove these duplicate groups. To do so, remove the unique constraint on the `ObjectGUID` attribute of the LDAP Group entity. Run the `Ldap.MF_DeleteDuplicateGroups` migration microflow to detect and remove duplicate LDAP Group records. After the cleanup is complete, add a unique constraint on the `ObjectGUID` attribute of the LDAP Group entity and **Refresh** groups. Run the [LDAP synchronization](/appstore/modules/ldap/#regular-synchronization) again. {{% /alert %}} ## Configuration{#configuration}