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

The specific number of domain controllers necessary in your network depends on the network
size and configuration. A minimum of two Active Directory domain controllers are
recommended for each domain. For more information, refer to the Active Directory
documentation, or to http://www.microsoft.com/Windows2000 and
http://windowsupdate.microsoft.com.
• Where will you get your name service data when migrating the data to the directory?
You can get the data from:
— /etc/passwd and /etc/group
— The same source files used to create your NIS maps, if using NIS
— The NIS maps
For information about importing information into the directory, refer to “Importing Name
Service Data into Your Directory” (page 35). For information on migration scripts, refer to
“Command, Tool, Schema Extension Utility, and Migration Script Reference” (page 163).
To add an individual user entry or modify an existing user entry in your directory, use the
ldapmodify command or other directory administration tools, such as the Active Directory
Users and Computers interface tool.
NOTE: Keep a small subset of users in /etc/passwd, particularly the root login. This
allows administrative users to log in during installation and testing. Also, if the directory
is unavailable you can still log in to the system.
• Where will name service data be located in your directory?
LDAP-UX Client Services, by default, expect user and group data to use the object classes
and attributes specified by RFC 2307. The migration scripts for Active Directory, by default,
populate the existing Users container. “Example Directory Structure for a Single Domain”
(page 26) shows a base DN of DC=cup, DC=hp, DC=com.
If you prefer to merge your name service data into an existing directory structure, you can
map the standard RFC 2307 attributes to alternate attributes. Refer to “LDAP-UX Client
Services Object Classes” (page 159).
• How will user and group data be migrated into your directory?
The migration scripts provided with LDAP-UX Client Services for Active Directory migrate
all user and group data to the "Users" container.
If you merge your data into an existing directory, for example, to share user names and
passwords with other applications, the migration scripts can create LDIF files of your user
data, but you must write your own scripts or use other tools to merge the data into your
directory. PosixAccount attributes can be added to your users already in the directory to
leverage your existing directory data.
Planning Your Installation 25