1 .TH LDAPDELETE 1 "RELEASEDATE" "OpenLDAP LDVERSION"
3 .\" Copyright 1998-2005 The OpenLDAP Foundation All Rights Reserved.
4 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 ldapdelete \- LDAP delete entry tool
22 .BI \-d \ debuglevel\fR]
32 .BI \-y \ passwdfile\fR]
36 .BI \-h \ ldaphost\fR]
38 .BI \-P \ 2\fR\||\|\fI3\fR]
40 .BI \-p \ ldapport\fR]
42 .BR \-O \ security-properties ]
65 is a shell-accessible interface to the
70 opens a connection to an LDAP server, binds, and deletes one or more
71 entries. If one or more \fIDN\fP arguments are provided, entries with
72 those Distinguished Names are deleted. Each \fIDN\fP should be provided
73 using the LDAPv3 string representation as defined in RFC 2253.
74 If no \fIdn\fP arguments
75 are provided, a list of DNs is read from standard input (or from
76 \fIfile\fP if the -f flag is used).
80 Show what would be done, but don't actually delete entries. Useful for
81 debugging in conjunction with -v.
84 Use verbose mode, with many diagnostics written to standard output.
87 Use Kerberos IV authentication instead of simple authentication. It is
88 assumed that you already have a valid ticket granting ticket. This option
91 is compiled with Kerberos support.
94 Same as \-k, but only does step 1 of the Kerberos IV bind. This is useful
95 when connecting to a slapd and there is no x500dsa.hostname principal
96 registered with your Kerberos Domain Controller(s).
99 Continuous operation mode. Errors are reported, but
101 will continue with deletions. The default is to exit after
105 Enable manage DSA IT control.
107 makes control critical.
110 Set the LDAP debugging level to \fIdebuglevel\fP.
112 must be compiled with LDAP_DEBUG defined for this option to have any effect.
115 Read a series of DNs from \fIfile\fP, one per line, performing an
116 LDAP delete for each.
119 Use simple authentication instead of SASL.
122 Use the Distinguished Name \fIbinddn\fP to bind to the LDAP directory.
125 Prompt for simple authentication.
126 This is used instead of specifying the password on the command line.
129 Use \fIpasswd\fP as the password for simple authentication.
132 Use complete contents of \fIpasswdfile\fP as the password for
133 simple authentication.
136 Specify URI(s) referring to the ldap server(s).
139 Specify an alternate host on which the ldap server is running.
140 Deprecated in favor of -H.
143 Specify an alternate TCP port where the ldap server is listening.
144 Deprecated in favor of -H.
146 .BI \-P \ 2\fR\||\|\fI3
147 Specify the LDAP protocol version to use.
150 Do a recursive delete. If the DN specified isn't a leaf, its
151 children, and all their children are deleted down the tree. No
152 verification is done, so if you add this switch, ldapdelete will
153 happily delete large portions of your tree. Use with care.
155 .BI \-O \ security-properties
156 Specify SASL security properties.
159 Enable SASL Interactive mode. Always prompt. Default is to prompt
163 Enable SASL Quiet mode. Never prompt.
166 Specify the authentication ID for SASL bind. The form of the identity depends on the
167 actual SASL mechanism used.
170 Specify the realm of authentication ID for SASL bind. The form of the realm
171 depends on the actual SASL mechanism used.
174 Specify the requested authorization ID for SASL bind.
176 must be one of the following formats:
178 .I <distinguished name>
184 Specify the SASL mechanism to be used for authentication. If it's not
185 specified, the program will choose the best mechanism the server knows.
188 Issue StartTLS (Transport Layer Security) extended operation. If you use
190 , the command will require the operation to be successful.
192 The following command:
195 ldapdelete "cn=Delete Me,dc=example,dc=com"
198 will attempt to delete the entry named "cn=Delete Me,dc=example,dc=com".
199 Of course it would probably be necessary to supply authentication
202 Exit status is 0 if no errors occur. Errors result in a non-zero exit
203 status and a diagnostic message being written to standard error.
213 The OpenLDAP Project <http://www.openldap.org/>
216 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
218 is derived from University of Michigan LDAP 3.3 Release.