Skip to content

Fortified IDDocs

Add Group To Members

Configuration reference for the Add Group To Members Pipes valve and its supported options.

Before using this valve the LdapClient module must be configured and deployed with matching name as defined in "namespace"

NameDescriptionDefaultMandatoryExpanded
namespaceBind to LdapClient module."default"
group_idGroup DN.
members_identifierJsonArray with member objects or member DN."@json:${request.ad_pending_add.all}"
id_propertyProperty on JSON object that contains the member DN."id"
{
"selected_ad_id" : "CN=Cert Publishers,CN=Users,DC=company,DC=local",
"ad_pending_add" : [
{
"id" : "CN=Felix Andreasson,OU=Demo,DC=company,DC=local",
"displayName" : "Felix Andreasson"
},
{
"id" : "CN=Eva Ek,OU=Demo,DC=company,DC=local",
"displayName" : "Eva Ek"
}
]
}

Every successful call publishes changes to the platform audit trail automatically — there is no audit flag to configure. Whether anything is actually recorded depends on whether an Audit module is deployed to consume it.

  • object_type group, package_type GroupMembershipAdded
  • object_id — the group's DN (group_id)
  • one change per member added, field member, after_value the member's DN
[
{ "field": "member", "after_value": "CN=Felix Andreasson,OU=Demo,DC=company,DC=local" },
{ "field": "member", "after_value": "CN=Eva Ek,OU=Demo,DC=company,DC=local" }
]

See Audit for how published changes are grouped into events and change packages, and for the built-in UI and REST API to view them.