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]
74 .BI \-d \ debuglevel\fR]
82 .BI \-h \ ldaphost\fR]
84 .BI \-p \ ldapport\fR]
86 .BI \-P \ 2\fR\||\|\fI3\fR]
92 .BI \-U \ username\fR]
103 is a shell-accessible interface to the
109 is implemented as a hard link to the ldapmodify tool. When invoked as
111 the -a (add new entry) flag is turned on automatically.
114 opens a connection to an LDAP server, binds, and modifies or adds entries.
115 The entry information is read from standard input or from \fIfile\fP through
116 the use of the -f option.
120 Add new entries. The default for
122 is to modify existing entries. If invoked as
124 this flag is always set.
127 Assume that any values that start with a `/' are binary values and that
128 the actual value is in a file whose path is specified in the place where
129 values normally appear.
132 Automatically chase referrals.
135 Continuous operation mode. Errors are reported, but
137 will continue with modifications. The default is to exit after
141 Replace existing values by default.
144 Show what would be done, but don't actually modify entries. Useful for
145 debugging in conjunction with -v.
148 Use verbose mode, with many diagnostics written to standard output.
151 Use Kerberos authentication instead of simple authentication. It is
152 assumed that you already have a valid ticket granting ticket. You must
153 compile with KERBEROS defined for this option to have any effect.
156 Same as \-k, but only does step 1 of the kerberos bind. This is useful
157 when connecting to a slapd and there is no x500dsa.hostname principal
158 registered with your kerberos servers.
161 Force application of all changes regardless of the contents of input
162 lines that begin with
164 (by default, replica: lines are compared against the LDAP server host
165 and port in use to decide if a replog record should actually be applied).
168 Enable manage DSA IT control.
170 makes control critical.
173 Set the LDAP debugging level to \fIdebuglevel\fP.
175 must be compiled with LDAP_DEBUG defined for this option to have any effect.
178 Read the entry modification information from \fIfile\fP instead of from
182 Use \fIbinddn\fP to bind to the LDAP directory. \fIbinddn\fP should be
183 a string-represented DN as defined in RFC 1779.
186 Prompt for simple authentication.
187 This is used instead of specifying the password on the command line.
190 Use \fIpasswd\fP as the password for simple authentication.
193 Specify an alternate host on which the ldap server is running.
196 Specify an alternate TCP port where the ldap server is listening.
198 .BI \-P \ 2\fR\||\|\fI3
199 Specify the LDAP protocol version to use.
201 .BI \-O \ security-properties
202 Specify SASL security properties.
205 Specify the username for SASL bind. The syntax of the username depends on the
206 actual SASL mechanism used.
209 Specify the requested authorization ID for SASL bind.
211 must be one of the following formats:
213 .I <distinguished name>
219 Specify the SASL mechanism to be used for authentication. If it's not
220 specified, the program will choose the best mechanism the server knows.
223 Issue StartTLS (Transport Layer Security) extended operation. If you use
225 , the command will require the operation to be successful.
227 The contents of \fIfile\fP (or standard input if no \-f flag is given on
228 the command line) should conform to the format defined in
229 .BR slapd.replog (5),
230 with the exceptions noted below.
232 If the first line of a record consists of a decimal number (entry id),
235 Lines that begin with "replica:" are matched against the LDAP server host
236 and port in use to decide if a particular replog record should be applied.
237 Any other lines that precede the "dn:" line are ignored.
238 The -F flag can be used to force
240 to apply all of the replog changes, regardless of the presence or
241 absence of any "replica:" lines.
243 If no "changetype:" line is present, the default is "add" if the -a
244 flag is set (or if the program was invoked as
246 and "modify" otherwise.
248 If changetype is "modify" and no "add:", "replace:", or "delete:" lines
249 appear, the default is "replace" if the -r flag is set and "add"
252 Note that the above exceptions to the
256 entries to be used as input to
260 .SH ALTERNATIVE INPUT FORMAT
261 An alternative input format is supported for compatibility with older
264 This format consists of one or more entries separated by blank lines,
265 where each entry looks like:
268 Distinguished Name (DN)
273 where \fIattr\fP is the name of the attribute and \fIvalue\fP is the
276 By default, values are added. If the
279 given, the default is to replace existing values with the new one.
280 Note that it is permissible for a given attribute to appear more than
281 once (for example, to add more than one value for an attribute). Also
282 note that you can use a trailing `\\' to continue values across lines and
283 preserve newlines in the value itself (this is useful for modifying
284 QUIPU iattr attributes among others).
287 should be preceded by a \fB-\fP to remove a value. The `=' and
288 value should be omitted to remove an entire attribute.
291 should be preceded by a \fB+\fP to add a value in the presence of the
295 Assuming that the file
297 exists and has the contents:
300 dn: cn=Modify Me, dc=OpenLDAP, dc=Org
303 mail: modme@OpenLDAP.org
309 jpegPhoto:< file://tmp/modme.jpeg
318 ldapmodify -b -r -f /tmp/entrymods
321 will replace the contents of the "Modify Me" entry's
323 attribute with the value "modme@OpenLDAP.org", add a
325 of "Grand Poobah", and the contents of the file "/tmp/modme.jpeg"
328 and completely remove the
331 The same modifications as above can be performed using the older
336 cn=Modify Me, dc=OpenLDAP, dc=org
337 mail=modme@OpenLDAP.org
339 +jpegPhoto=/tmp/modme.jpeg
346 ldapmodify -b -r -f /tmp/entrymods
349 Assuming that the file
351 exists and has the contents:
354 dn: cn=Barbara Jensen, dc=OpenLDAP, dc=org
359 title: the world's most famous mythical manager
360 mail: bjensen@OpenLDAP.org
366 ldapadd -f /tmp/entrymods
369 will add a new entry for Babs Jensen, using the values from the
373 Assuming that the file
375 exists and has the contents:
378 dn: cn=Barbara Jensen, dc=OpenLDAP, dc=org
384 ldapmodify -f /tmp/entrymods
387 will remove Babs Jensen's entry.
389 Exit status is 0 if no errors occur. Errors result in a non-zero exit
390 status and a diagnostic message being written to standard error.
405 .IR "A String Representation of Distinguished Names",
408 ISODE Consortium, March 1995.
410 There is no interactive mode, but there probably should be.
412 The OpenLDAP Project <http://www.openldap.org/>
415 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
417 is derived from University of Michigan LDAP 3.3 Release.