Add Group To Members
Configuration reference for the Add Group To Members Pipes valve and its supported options.
Introduction
Section titled “Introduction”Before using this valve the LdapClient module must be configured and deployed with matching name as defined in "namespace"
Configuration
Section titled “Configuration”| Name | Description | Default | Mandatory | Expanded |
|---|---|---|---|---|
namespace | Bind to LdapClient module. | "default" | ||
group_id | Group DN. | |||
members_identifier | JsonArray with member objects or member DN. | "@json:${request.ad_pending_add.all}" | ||
id_property | Property on JSON object that contains the member DN. | "id" |
{ "name": "ActiveDirectoryAddGroupToMembers", "config": { "namespace": "ldap01", "id_property": "id", "group_id": "${request.selected_ad_id}", "members_identifier": "@json:${request.ad_pending_add.all}" }}Example pipe data
Section titled “Example pipe data”{"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_typegroup,package_typeGroupMembershipAddedobject_id— the group's DN (group_id)- one change per member added,
fieldmember,after_valuethe 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.