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

Glossary
Access Control
Instruction
A specification controlling access to entries in a directory.
Access Control
List
One or more ACIs.
ACI See See Access Control Instruction.
ACL See See Access Control List..
Configuration
profile
An entry in an LDAP directory containing information common to many clients, that allows
clients to access user, group and other information in the directory. Clients download the profile
from the directory.
See also See also Client Configuration File..
Global Catalog
Server (GCS)
This refers to the domain controller, which hosts the global catalog for a forest. The global
catalog contains partial information of each domain. LDAP-UX utilizes this feature to find out
which domain a queried data belongs to. The root domain is the default GCS.
IETF Internet Engineering Task Force; the organization that defines the LDAP specification. See
http://www.ietf.org.
KDC Key Distribution Center. A computer that issues the session key necessary for the client and
server to communicate in a Kerberos environment.
Kerberos An authentication protocol designed for open, hostile networks. Developed by MIT.
LDAP See See Lightweight Directory Access Protocol.
LDAP Data
Interchange
Format (LDIF)
The format used to represent directory server entries in text form.
LDIF See See LDAP Data Interchange Format.
Lightweight
Directory Access
Protocol (LDAP)
A standard, extensible set of conventions specifying communication between clients and servers
across TCP/IP network connections.
See also See also SLAPD..
Local Domain This refers to the domain that you first configure using the LDAP-UX setup tool and after
choosing Windows 2000 or 2003 ADS as your directory server. This is also the only domain
you configure if you just choose a single domain in which to store your POSIX information.
When LDAP-UX retrieves POSIX information, the local domain is always the first domain
searched. If the entry is found in the local domain, searching stops, therefore, the local domain
will be the primary domain in which you store frequently accessed information. Its profile
configuration is /etc/opt/ldapux/ldapux_profile.bin
Multiple
Domains
The supported multiple domains refer to domains in an ADS forest. Domains from different
forests are not supported.
Name Service
Switch (NSS)
A framework that allows a host to get name information from various sources such as local
files in /etc, NIS, NIS+, or an LDAP directory without modifying applications. See switch(4) for
more information.
Network
Information
Service (NIS)
A distributed database system providing centralized management of common configuration
files, such as /etc/passwd and /etc/hosts.
NIS See See Network Information Service.
NSS See See Name Service Switch.
PAM See See Pluggable Authentication Mechanism.
Pluggable
Authentication
A framework that allows different authentication service modules to be made available without
modifying applications. See pam_ldap(5), pam(3), and pam.conf(4) for more information.
Mechanism
(PAM)
Profile See See Configuration profile.
279