LDAP Delete
Configuration reference for the LDAP Delete Pipes valve and its supported options.
Introduction
Section titled “Introduction”Operates on the current item. By default item.id() is used as the LDAP DN. If dn_parameter is set, that value is used instead.
Prerequisites
Section titled “Prerequisites”Before using this valve the LdapClient module must be configured and deployed.
Configuration
Section titled “Configuration”Common LDAP valve configuration can be found here.
| Name | Description | Default | Mandatory | Expanded |
|---|---|---|---|---|
dn_parameter | If not using item.id() as DN value. | N/A |
{ "name": "LDAPDelete", "config": { "destination": "default", "dn_parameter": "${item.dn}" }}Every successful delete operation publishes a change to the platform audit trail automatically — there is no audit flag to configure on the valve or the LdapClient anymore. Whether anything is actually recorded depends on whether an Audit module is deployed to consume it.
{ "name": "LDAPDelete", "config": {}}[ { "field": "dn", "after_value": "uid=demo,dc=example,dc=com" }]object_typeuser,package_typeUserDeleted— always, regardless of what kind of entry is actually deletedobject_id— the DN of the deleted entry, taken fromitem.id()(ordn_parameter)- a single change is published,
fielddn, since the entry is removed in its entirety
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.