# Delete LDAP Entry

div
div
Client SDK
div
Backend API
div
Mobile approve
div
SSO
div
Sub-journey
> Delete a specific LDAP entry from the external LDAP or Active Directory.


## Description

This step performs an LDAP delete operation to remove an entry from an external LDAP or Active Directory. Other journey steps may be used to add entries, bind entries, modify entries, modify passwords of entries, or search entries.

You can specify the LDAP by selecting either an LDAP connection or Active Directory connection. The LDAP entry to delete is specified by the DN (distinguished name).

If the step is successfully completed, the journey continues to the next step, and result data is outputted to a specified variable (if configured).

## Configuration

div
| Field | Description |
|  --- | --- |
| **LDAP Provider** | The LDAP connection or Active Directory connection to use |
| **DN** | Distinguished name (DN) that uniquely identifies an entry and describes its position in the database. For example: CN=Groups,OU=useast,DC=yourorg,DC=com |
| **Output Variable** | Name of the variable used to store the result data created by this step. This data represents the LDAP response. |


## Result Data

The output variable stores the step response object with the following structure:

| Field | Description |
|  --- | --- |
| `is_successful` | Boolean. LDAP response which includes the status of the step (success or failure). |
| `result_code` | Number. LDAP response which includes a numeric result code to categorize the reason for the success or failure. |
| `error_message` | String. LDAP response message that is included with the result code. |


{% admonition type="info" name="Journey event data" %}
This step can be configured to record step input and output data, or a custom payload, which is then surfaced in journey events in Journey Analytics for diagnostic purposes. For details, see [Additional data reporting](/guides/orchestration/getting-started/event_reporting.md).
{% /admonition %}