From 4b6f9077bfb8e720df364c61bd3aaab076236698 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Tue, 18 Aug 2026 09:20:46 -0400 Subject: [PATCH] docs(dashboard): surface the short-name GroupToTag key constraint in the class summary The consequence that full-DN keys can never match (the shared LDAP provider pre-strips groups to short RDN names) was documented only in MapGroupsToTags's lookup comment; the class-level now states it and points there, mirroring DashboardGroupRoleMapping. --- .../Dashboard/DashboardGroupTagMapping.cs | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/ZB.MOM.WW.MxGateway.Server/Dashboard/DashboardGroupTagMapping.cs b/src/ZB.MOM.WW.MxGateway.Server/Dashboard/DashboardGroupTagMapping.cs index 84be574..7e3b750 100644 --- a/src/ZB.MOM.WW.MxGateway.Server/Dashboard/DashboardGroupTagMapping.cs +++ b/src/ZB.MOM.WW.MxGateway.Server/Dashboard/DashboardGroupTagMapping.cs @@ -6,6 +6,9 @@ namespace ZB.MOM.WW.MxGateway.Server.Dashboard; /// Sibling of and deliberately follows /// the same group-matching rules (full DN first, leading-RDN fallback, /// case-insensitive) so operators write one kind of group key for both maps. +/// Because the shared LDAP provider delivers groups already stripped to short +/// RDN names, full-DN GroupToTag keys can never match — use short group +/// names as keys (see the lookup comment in ). /// Tags gate dashboard event VISIBILITY only; they are never a data-access /// constraint. ///