LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)
Table Of Contents
- LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Administrator's Guide
- Table of Contents
- Preface
- 1 Introduction
- 2 Installing LDAP-UX Client Services
- Before You Begin
- Summary of Installing and Configuring LDAP-UX Client Services
- Planning Your Installation
- Installing LDAP-UX Client Services on a Client
- Configuring Active Directory for HP-UX Integration
- Step 1: Install Active Directory
- Step 2: Install SFU 2.0, 3.0 or 3.5 including Server for NIS
- Step 3: Create a Proxy User
- Step 4: Add an HP-UX Client Machine Account to Active Directory
- Step 5: Use ktpass to Create the Keytab File for the HP-UX client machine
- Step 6: Add POSIX Attributes into the Global Catalog
- Importing Name Service Data into Your Directory
- Configuring LDAP-UX Client Services
- Step 1: Run the Setup Program
- Step 2: Install the PAM Kerberos Product
- Step 3: Configure Your HP-UX Machine to Authenticate Using PAM Kerberos
- Step 4: Configure the Name Service Switch (NSS)
- Step 5: Configure the PAM Authorization Service Module (pam_authz)
- Step 6: Configure the Disable Login Flag
- Step 7: Verify LDAP-UX Client Services for Single Domain
- Step 8: Configure Subsequent Client Systems
- Configuring the LDAP-UX Client Services with SSL or TLS Support
- Downloading the Profile Periodically
- 3 Active Directory Multiple Domains
- 4 LDAP-UX Client Services with AutoFS Support
- 5 LDAP Printer Configurator Support
- 6 Dynamic Group Support
- 7 Administering LDAP-UX Client Services
- Using the LDAP-UX Client Daemon
- Integrating with Trusted Mode
- SASL GSSAPI Support
- PAM_AUTHZ Login Authorization
- Policy And Access Rules
- How Login Authorization Works
- PAM_AUTHZ Supports Security Policy Enforcement
- Policy File
- Policy Validator
- Dynamic Variable Support
- Constructing an Access Rule in pam_authz.policy
- Static List Access Rule
- Dynamic Variable Access Rule
- Security Policy Enforcement with Secure Shell (SSH) or r-commands
- Adding Additional Domain Controllers
- Adding Users, Groups, and Hosts
- User and Group Management
- Displaying the Proxy User's Distinguished Name
- Verifying the Proxy User
- Creating a New Proxy User
- Displaying the Current Profile
- Creating a New Profile
- Modifying a Profile
- Changing Which Profile a Client is Using
- Creating an /etc/krb5.keytab File
- Considering Performance Impacts
- Client Daemon Performance
- Troubleshooting
- 8 Modifying User Information
- 9 Mozilla LDAP C SDK
- A Configuration Worksheet
- B LDAP-UX Client Services Object Classes
- C Command, Tool, Schema Extension Utility, and Migration Script Reference
- LDAP-UX Client Services Components
- Client Management Tools
- LDAP User and Group Management Tools
- Environment Variables
- Return Value Formats
- Common Return Codes
- The ldapuglist Tool
- The ldapugadd Tool
- The ldapugmod Tool
- The ldapugdel Tool
- The ldapcfinfo Tool
- LDAP Directory Tools
- Schema Extension Utility
- Name Service Migration Scripts
- Unsupported Contributed Tools and Scripts
- D Sample PAM Configuration File
- E Sample /etc/krb5.conf File
- F Sample /etc/pam.conf File for HP-UX 11i v1 Trusted Mode
- G Sample /etc/pam.conf File for HP-UX 11i v2 Trusted Mode
- H Sample PAM Configuration File for Security Policy Enforcement
- Glossary
- Index

Warnings
Under common usage, ldapugmod uses the LDAP replace operation when changing values of
an attribute in an entry. This feature can impact attributes that have multiple values, by removing
all occurrences of an attribute value and replacing it with the one specified on the ldapugmod
command line. For example, if the -n argument is used to specify a new name for a posixGroup,
all occurances of the cn attribute are replaced by the value specified for the -n argument. This
mode of operation applies to all command argument specified values, including -u, -g, -s, -d,
-I and -c.
When you use the <attr>=<value> parameter to modify an existing attribute, the ldapugmod
command also uses the LDAP replace operation. The replace operation removes all occurrences
of the specified attribute for an entry and replaces it with the value specified. If there are multiple
values for a single attribute in an entry, the use of a single <attr>=<value> parameter will
replace all values with the single value specified on the command line. You can specify more
than one occurrence of the same attribute on the command line, if that attribute is multi-valued.
In that case, both values are created in the entry.
Use of -A or -R changes this behavior (for both the above-listed command arguments and the
<attr>=<value> parameter). Any attribute specified as an argument to the -A or -R causes
ldapugmod to perform an LDAP add operation instead of an LDAP replace operation.
NOTE: The ldapugmod tool does not allow you to use the same attribute and value pair more
than once, either as part of <attr>=<value>, -R or -A, or with other command line options.
The ldapugmod tool exits with error status before sending any conflict modification request to
the LDAP directory server.
Example 1
In this example, an entry in an LDAP directory is as follows:
dn: uid=mLee,ou=users,dc=example,dc=com
cn: Mark Lee
cn: Michael Lee
uid: mlee
uidNumber: 2200
gidNumber: 212
homeDirectory: /home/mlee
loginShell: /usr/bin/sh
gecos: Mark Lee,New York,555-666-6000
description: test user entry
description: multi-valued attribute entry
Perform the following ldapugmod command for the user entry, mlee:
cd /opt/ldapux/bin
./ldapugmod -t passwd mlee "cn=Mackey Lee"
The above commands replace all instances of cn with the single value, Mackey Lee. The resulting
mlee entry is as follows:
dn: uid=mLou,ou=users,dc=org,dc=example,dc=com
cn: Mackey Lee
uid: mlee
uidNumber: 2200
gidNumber: 212
homeDirectory: /home/mlee
loginShell: /usr/bin/sh
gecos: Mack Lee,New York,555-666-6000
description: test user entry
description: multi-valued attribute entry
Perform the following ldapugmod command for the user entry, mlee:
208 Command, Tool, Schema Extension Utility, and Migration Script Reference