1 .TH LDAPMODIFY 1 "12 July 2000" "OpenLDAP LDVERSION"
3 .\" Copyright 1998-2000 The OpenLDAP Foundation All Rights Reserved.
4 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 ldapmodify, ldapadd \- LDAP modify entry and LDAP add entry tools
30 .BI \-d \ debuglevel\fR]
38 .BI \-h \ ldaphost\fR]
40 .BI \-p \ ldapport\fR]
42 .BI \-P \ 2\fR\||\|\fI3\fR]
44 .BR \-O \ security-properties ]
46 .BI \-U \ username\fR]
76 .BI \-d \ debuglevel\fR]
84 .BI \-h \ ldaphost\fR]
86 .BI \-p \ ldapport\fR]
88 .BI \-P \ 2\fR\||\|\fI3\fR]
94 .BI \-U \ username\fR]
105 is a shell-accessible interface to the
111 is implemented as a hard link to the ldapmodify tool. When invoked as
113 the -a (add new entry) flag is turned on automatically.
116 opens a connection to an LDAP server, binds, and modifies or adds entries.
117 The entry information is read from standard input or from \fIfile\fP through
118 the use of the -f option.
122 Add new entries. The default for
124 is to modify existing entries. If invoked as
126 this flag is always set.
129 Assume that any values that start with a `/' are binary values and that
130 the actual value is in a file whose path is specified in the place where
131 values normally appear.
134 Automatically chase referrals.
137 Continuous operation mode. Errors are reported, but
139 will continue with modifications. The default is to exit after
143 Replace existing values by default.
146 Show what would be done, but don't actually modify entries. Useful for
147 debugging in conjunction with -v.
150 Use verbose mode, with many diagnostics written to standard output.
153 Use Kerberos authentication instead of simple authentication. It is
154 assumed that you already have a valid ticket granting ticket. You must
155 compile with KERBEROS defined for this option to have any effect.
158 Same as \-k, but only does step 1 of the kerberos bind. This is useful
159 when connecting to a slapd and there is no x500dsa.hostname principal
160 registered with your kerberos servers.
163 Force application of all changes regardless of the contents of input
164 lines that begin with
166 (by default, replica: lines are compared against the LDAP server host
167 and port in use to decide if a replog record should actually be applied).
170 Enable manage DSA IT control.
172 makes control critical.
175 Set the LDAP debugging level to \fIdebuglevel\fP.
177 must be compiled with LDAP_DEBUG defined for this option to have any effect.
180 Read the entry modification information from \fIfile\fP instead of from
184 Use simple authentication instead of SASL.
187 Use \fIbinddn\fP to bind to the LDAP directory. \fIbinddn\fP should be
188 a string-represented DN as defined in RFC 1779.
191 Prompt for simple authentication.
192 This is used instead of specifying the password on the command line.
195 Use \fIpasswd\fP as the password for simple authentication.
198 Specify an alternate host on which the ldap server is running.
201 Specify an alternate TCP port where the ldap server is listening.
203 .BI \-P \ 2\fR\||\|\fI3
204 Specify the LDAP protocol version to use.
206 .BI \-O \ security-properties
207 Specify SASL security properties.
210 Specify the username for SASL bind. The syntax of the username depends on the
211 actual SASL mechanism used.
214 Specify the requested authorization ID for SASL bind.
216 must be one of the following formats:
218 .I <distinguished name>
224 Specify the SASL mechanism to be used for authentication. If it's not
225 specified, the program will choose the best mechanism the server knows.
228 Issue StartTLS (Transport Layer Security) extended operation. If you use
230 , the command will require the operation to be successful.
232 The contents of \fIfile\fP (or standard input if no \-f flag is given on
233 the command line) should conform to the format defined in
234 .BR slapd.replog (5),
235 with the exceptions noted below.
237 If the first line of a record consists of a decimal number (entry id),
240 Lines that begin with "replica:" are matched against the LDAP server host
241 and port in use to decide if a particular replog record should be applied.
242 Any other lines that precede the "dn:" line are ignored.
243 The -F flag can be used to force
245 to apply all of the replog changes, regardless of the presence or
246 absence of any "replica:" lines.
248 If no "changetype:" line is present, the default is "add" if the -a
249 flag is set (or if the program was invoked as
251 and "modify" otherwise.
253 If changetype is "modify" and no "add:", "replace:", or "delete:" lines
254 appear, the default is "replace" if the -r flag is set and "add"
257 Note that the above exceptions to the
261 entries to be used as input to
265 .SH ALTERNATIVE INPUT FORMAT
266 An alternative input format is supported for compatibility with older
269 This format consists of one or more entries separated by blank lines,
270 where each entry looks like:
273 Distinguished Name (DN)
278 where \fIattr\fP is the name of the attribute and \fIvalue\fP is the
281 By default, values are added. If the
284 given, the default is to replace existing values with the new one.
285 Note that it is permissible for a given attribute to appear more than
286 once (for example, to add more than one value for an attribute). Also
287 note that you can use a trailing `\\' to continue values across lines and
288 preserve newlines in the value itself (this is useful for modifying
289 QUIPU iattr attributes among others).
292 should be preceded by a \fB-\fP to remove a value. The `=' and
293 value should be omitted to remove an entire attribute.
296 should be preceded by a \fB+\fP to add a value in the presence of the
300 Assuming that the file
302 exists and has the contents:
305 dn: cn=Modify Me, dc=OpenLDAP, dc=Org
308 mail: modme@OpenLDAP.org
314 jpegPhoto:< file://tmp/modme.jpeg
323 ldapmodify -b -r -f /tmp/entrymods
326 will replace the contents of the "Modify Me" entry's
328 attribute with the value "modme@OpenLDAP.org", add a
330 of "Grand Poobah", and the contents of the file "/tmp/modme.jpeg"
333 and completely remove the
336 The same modifications as above can be performed using the older
341 cn=Modify Me, dc=OpenLDAP, dc=org
342 mail=modme@OpenLDAP.org
344 +jpegPhoto=/tmp/modme.jpeg
351 ldapmodify -b -r -f /tmp/entrymods
354 Assuming that the file
356 exists and has the contents:
359 dn: cn=Barbara Jensen, dc=OpenLDAP, dc=org
364 title: the world's most famous mythical manager
365 mail: bjensen@OpenLDAP.org
371 ldapadd -f /tmp/entrymods
374 will add a new entry for Babs Jensen, using the values from the
378 Assuming that the file
380 exists and has the contents:
383 dn: cn=Barbara Jensen, dc=OpenLDAP, dc=org
389 ldapmodify -f /tmp/entrymods
392 will remove Babs Jensen's entry.
394 Exit status is 0 if no errors occur. Errors result in a non-zero exit
395 status and a diagnostic message being written to standard error.
410 .IR "A String Representation of Distinguished Names",
413 ISODE Consortium, March 1995.
415 There is no interactive mode, but there probably should be.
417 The OpenLDAP Project <http://www.openldap.org/>
420 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
422 is derived from University of Michigan LDAP 3.3 Release.