ldapugdel.1m (2010 09)

l
ldapugdel(1M) ldapugdel(1M)
NAME
ldapugdel - remove existing accounts or groups from an LDAP directory server
SYNOPSIS
ldapugdel [options ][-t type ][
-h hostname ][-p port ][-O [protAttr[
,...]]]
{
-D DN | uid_name | group_name}
DESCRIPTION
ldapugdel is used to remove POSIX related user or group entries from the directory server. With the
-O option, ldapugdel can be used to remove POSIX related attributes and objectclasses from user or
group entries, without removing the entry itself.
Options
-P Prompt for the administrators bind identity (typically LDAP DN or kerberos principal) and bind
password. Without -P ldapugdel will discover the bind identity and password from the
environment variable LDAP_BINDDN and LDAP_BINDCRED
. If the LDAP_BINDDN or
LDAP_BINDCRED environment variable has not been specified,
ldapugdel will follow the bind
configuration specified in the ldapux (5) configuration profile.
If ldapux (5) has specified "proxy" bind, the bind credential will be read from either the
/etc/opt/ldapux/acred
or /etc/opt/ldapux/pcred file. The acred file will only be
used by users that have sufficient administrative privilege to read that file. Refer to Binding to
the Directory Server below for additional details.
-x Used only with the -O option, forces ldapugdel to remove the uid , cn, and description attri-
butes for either a user or group entry, respectively.
Because use of
-x removes common attributes typically used by other LDAP-enabled applica-
tions, use of it is rarely recommended when removing posixAccount or posixGroup related attri-
butes. If removal of the uid, cn,ordescription would cause an objectclass violation, a warning
message would be generated. -x will try to remove as many attributes as allowed by the direc-
tory server.
-y Used only with the combined with -O and the -t passwd options, forces
ldapugdel to
remove the userPassword attribute from the user entry.
Use of
-y is rarely recommended when removing posixAccount related attributes.
-Z Requires an SSL connection to the directory server, even if the ldapux (5) configuration does not
require the use of SSL.
Use of
-Z requires either a valid server or CA certificate be defined in the
/etc/opt/ldapux/cert8.db
file. An error will occur if the SSL connection could not be
established.
-ZZ Attempt a TLS connection to the directory server, even if the ldapux (5) configuration does not
require the use of TLS. If a TLS connection is unable to be established a non-TLS and non-SSL
connection will be established.
Use of
-ZZ is not recommended unless alternative methods are used to protect from network
eavesdropping. Use of -ZZ requires either a valid server or CA certificate be defined in the
/etc/opt/ldapux/cert8.db file. Refer to Binding to the Directory Server below for addi-
tional details.
-ZZZ Requires a TLS connection to the directory server, even if the ldapux (5) configuration does not
require the use of TLS. Use of -ZZZ requires either a valid server or CA certificate be defined in
the /etc/opt/ldapux/cert8.db file. An error will occur if the TLS connection could not be
established. Refer to Binding to the Directory Server below for additional details.
-S Upon successful completion, displays the DN of the deleted/updated entry.
Arguments
-h hostname Specifies the host name and optional port number (hostname:port) of the directory
server. This option overrides the server list configured by ldapux (5).
The hostname field also supports specification of IPv4 and IPv6 addresses. Note that
when a port is specified for an IPv6 address, the IPv6 address must be specified in
square-bracketed form. If the optional port is unspecified, the port number is assumed to
HP-UX 11i v3: June 2010 Web Release 1 Hewlett-Packard Company 1

Summary of content (6 pages)