Penguin
 
ldapadd(1)
LikePages

LDAPMODIFY

LDAPMODIFY

NAME SYNOPSIS DESCRIPTION OPTIONS INPUT FORMAT EXAMPLES DIAGNOSTICS SEE ALSO BUGS AUTHOR ACKNOWLEDGEMENTS


NAME

ldapmodify, ldapadd - LDAP modify entry and LDAP add entry tools

SYNOPSIS

ldapmodify [__-a__ [__-c__ [__-n__ [__-v__ [__-k__ [__-K__ [__-M[[M] [__-d__ ''debuglevel'' [__-D__ ''binddn'' [__-W__ [__-w__ ''passwd'' [unrenderable node] [__-h__ ''ldaphost'' [unrenderable node] [__-P__ ''2'' [unrenderable node] [__-I__ [__-Q__ [__-U__ ''authcid'' [__-x__ [unrenderable node] [__-Y__ ''mech'' [__-Z[[Z__] [__-f__ ''file''

ldapadd [__-c__ [__-n__ [__-v__ [__-k__ [__-K__ [__-M[[M] [unrenderable node] [__-D__ ''binddn'' [__-W__ [__-w__ ''passwd'' [__-h__ ''ldaphost'' [__-p__ ''ldapport'' [__-P__ ''2'' [__-O__ security-properties__ [__-I__ [__-Q__ [__-U__ ''authcid'' [__-x__ [__-X__ ''authzid'' [__-Y__ ''mech'' [__-Z[[Z__] [__-f__ ''file''

DESCRIPTION

ldapmodify is a shell-accessible interface to the ldap_modify(3) and __ldap_add__(3) library calls. ldapadd is implemented as a hard link to the ldapmodify tool. When invoked as ldapadd the -a (add new entry) flag is turned on automatically.

ldapmodify opens a connection to an LDAP server, binds, and modifies or adds entries. The entry information is read from standard input or from file through the use of the -f option.

OPTIONS

-a

Add new entries. The default for ldapmodify is to modify existing entries. If invoked as ldapadd, this flag is always set.

-c

Continuous operation mode. Errors are reported, but ldapmodify will continue with modifications. The default is to exit after reporting an error.

-n

Show what would be done, but don't actually modify entries. Useful for debugging in conjunction with -v.

-v

Use verbose mode, with many diagnostics written to standard output.

-k

Use Kerberos IV authentication instead of simple authentication. It is assumed that you already have a valid ticket granting ticket. You must compile with Kerberos support for this option to have any effect.

-K

Same as -k, but only does step 1 of the Kerberos IV bind. This is useful when connecting to a slapd and there is no x500dsa.hostname principal registered with your Kerberos Domain Controller(s).

-F

Force application of all changes regardless of the contents of input lines that begin with replica: (by default, replica: lines are compared against the LDAP server host and port in use to decide if a replog record should actually be applied).

-M[M

Enable manage DSA IT control. -MM makes control critical.

-d debuglevel

Set the LDAP debugging level to debuglevel. ldapmodify must be compiled with LDAP_DEBUG defined for this option to have any effect.

-f file

Read the entry modification information from file instead of from standard input.

-x

Use simple authentication instead of SASL.

-D binddn

Use the Distinguished Name binddn to bind to the LDAP directory.

-W

Prompt for simple authentication. This is used instead of specifying the password on the command line.

-w passwd

Use passwd as the password for simple authentication.

-H ldapuri

Specify URI(s) referring to the ldap server(s).

-h ldaphost

Specify an alternate host on which the ldap server is running. Deprecated in favor of -H.

-p ldapport

Specify an alternate TCP port where the ldap server is listening. Deprecated in favor of -H.

-P 2|3

Specify the LDAP protocol version to use.

-O security-properties

Specify SASL security properties.

-I

Enable SASL Interactive mode. Always prompt. Default is to prompt only as needed.

-Q

Enable SASL Quiet mode. Never prompt.

-U authcid

Specify the authentication ID for SASL bind. The form of the ID depends on the actual SASL mechanism used.

-X authzid

Specify the requested authorization ID for SASL bind. authzid must be one of the following formats: dn: or u:

-Y mech

Specify the SASL mechanism to be used for authentication. If it's not specified, the program will choose the best mechanism the server knows.

-Z[Z

Issue StartTLS (Transport Layer Security) extended operation. If you use -ZZ, the command will require the operation to be successful.

INPUT FORMAT

The contents of file (or standard input if no -f flag is given on the command line) should conform to the format defined in slapd.replog(5), with the exceptions noted below.

Lines that begin with ldapmodify to apply all of the replog changes, regardless of the presence or absence of any

If no ldapmodify) and

If changetype is ldapmodify__(1) for ldapadd(1).

Note that the above exceptions to the slapd.replog(5) format allow ldif(5) entries to be used as input to ldapmodify or ldapadd.

EXAMPLES

Assuming that the file /tmp/entrymods exists and has

the contents
dn: cn=Modify Me, dc=example, dc=com

changetype: modify replace: mail mail: modme@OpenLDAP.org - add: title title: Grand Poobah - add: jpegPhoto jpegPhoto:

the command
ldapmodify -r -f /tmp/entrymods

will replace the contents of the mail attribute with the value title of jpegPhoto, and completely remove the description'' attribute.

Assuming that the file /tmp/newentry exists and has

the contents
dn: cn=Barbara Jensen, dc=example, dc=com

objectClass: person cn: Barbara Jensen cn: Babs Jensen sn: Jensen title: the world's most famous mythical manager mail: bjensen@example.com uid: bjensen the command: ldapadd -f /tmp/entrymods will add a new entry for Babs Jensen, using the values from the file /tmp/newentry.

Assuming that the file /tmp/newentry exists and has

the contents
dn: cn=Barbara Jensen, dc=example, dc=com

changetype: delete the command: ldapmodify -f /tmp/entrymods will remove Babs Jensen's entry.

DIAGNOSTICS

Exit status is zero if no errors occur. Errors result in a non-zero exit status and a diagnostic message being written to standard error.

SEE ALSO

ldapadd(1), ldapdelete(1), ldapmodrdn(1), ldapsearch(1), ldap.conf(5), ldap(3), __ldap_add__(3), ldap_delete(3), __ldap_modify__(3), ldap_modrdn(3), __slapd.replog__(5)

BUGS

There is no interactive mode, but there probably should be.

AUTHOR

The OpenLDAP Project

ACKNOWLEDGEMENTS

OpenLDAP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OpenLDAP is derived from University of Michigan LDAP 3.3 Release.


This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.