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

-d <home_directory>
Replaces the full path name (including the user name) of the user’s
home directory. If the <home_directory> argument is an empty
string (a pair of double quotes: ""), ldapugmod removes the
homeDirectory or mapped attribute.
-m
Move the user’s home directory to the location specified with the
-d option. -m requires that you also specify the -d option. If the
specified <home_directory> already exists, the user’s current
home directory does not exist or the user running ldapugmod
does not have sufficient permissions to move the directory,
ldapugmod returns an error.
-I <gecos> Replaces gecos fields for the user. If <gecos> is an empty string,
ldapugmod removes the gecos or mapped attribute(s).
Typically the gecos argument contains four fields which represent
in the following order:
• The user’s full name
• The user’s work location
• The user’s work telephone number
• The user’s home telephone number (often omitted)
Each field in the <gecos> argument must be separated by a
comma. Although the fields specified within the <gecos>
argument can contain white space (such as “Bill Smith,Building
6,555-1234”). White space cannot be used between each field and
the separating commas.
LDAP-UX supports attribute mapping of the gecos field to
multiple attributes. If attribute mapping has been specified in the
LDAP-UX configuration profile, each field is mapped to its
representative attribute, in the order specified.
WARNING! If you specify the -I option and you have defined
attribute mapping for the gecos attribute, be careful not to specify
the same attributes in the command line that are also used in the
gecos map. In the following example, the gecos attribute has
been mapped to cn, l, and telephoneNumber attributes. The
following command can produce unpredictable results:
ldapugmod -I “lisa Hu,Austine,222-1234” lhu "cn=lisa
Hu” “sn=Hu”\
“telePhoneNumber=222-1234”
In the above example, because of the gecos attribute mapping,
the cn and telephoneNumber are specified twice, it results an
error when the same attribute and value are added to the directory
server. Use the ldapcfinfo tool to check gecos attribute
mapping configuration.
If the <gecos> argument is an empty string, ldapugmod removes
the gecos or mapped attributes. HP does not recommend that
you use the -I option, because the gecos attribute is often
mapped to required attributes. See the “WARNING” section below
for impacts when using this option.
-c <comment> Replaces a comment that will be stored in the description
attribute as defined by RFC 2307. LDAP-UX does not support
attribute mappings for the description attribute.
<attr>=<value>
Enables modification of arbitrary LDAP attributes and values. The
<value> parameter may be an empty string. However this usage
does not remove attributes and their values from the directory
206 Command, Tool, Schema Extension Utility, and Migration Script Reference