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 Active Directory must be installed separately after the Windows 2003 Server installation has
been completed on your computer. Use the following steps to install the Acitve Directory Server
on the Windows 2003:
1. The Prelimary Steps screen is displayed, select Configure Your Server Wizard.
2. The Server Role screen is displayed, select Domain Controller (Active Directory), then
click Next buttom.
3. Install any additional Administrative tools required for you to manage Active Directory.
These Windows 2003 Administrative tools are included with Windows 2003 Server to simplify
directory administration.
4. If ADS multiple domains will be used, set up the ADS forest. Ideally, the local domain should
contain the most frequently accessed data.
Step 2: Install SFU 2.0, 3.0 or 3.5 including Server for NIS
POSIX accounts have some attributes, such as user ID, login shell, and home directory, which
are not used by Windows 2000 or 2003. To use Active Directory as a data repository for HP-UX
users, the Active Directory schema needs to be extended to include the POSIX schema defined
in RFC 2307. Server for NIS, a tool available with the Services for Unix (SFU) add-on package,
extends the Active Directory schema based on RFC 2307 to allow integration of POSIX attributes.
IMPORTANT: When installing SFU version 2.0, ensure that you choose Customized Installation
at the Installation Options screen. This allows you to select the Server for NIS component for
installation.
When installing SFU version 3.0 or 3.5, the Server for NIS will be installed by default.
For corresponding Windows objects that exist in Active Directory (such as password and group),
Server for NIS adds POSIX attributes to the same object creating a unique object representing
both POSIX and Windows identities.
For example, information needed for a UNIX user is stored in Active Directory as part of the
Active Directory Domain Users group. To allow storing POSIX attributes, Server for NIS extends
the Users group with msSFUPosixAccount as its auxiliary class (SFU version 2.0). This allows
POSIX attributes to be added to newly created objects of the User class.
Version of SFU above 2.0 include the version string in these attribute names (i.e. msSFU30IpServic).
More information on SFU can be found on the Microsoft web site at
http://www.microsoft.com/windows2000/sfu/.
NOTE: Windows 2003 Release 2 (R2) Active Directory Server provides the RFC2307 schema
which is compliant with the IETF RFC2307 standard.
Step 3: Create a Proxy User
The use of a proxy user is mandatory for Active Directory, as anonymous binding done not grant
enough access rights to retrieve user, group, or any other name service data.
Use the Windows 2000 management tool, Active Directory Users and Computers, to
add a proxy user as a member of the "Domain Users" group. The proxy user is used by the
LDAP-UX clients to bind to the ADS for access to the name service data on the ADS. For example,
you might add a user:
Configuring Active Directory for HP-UX Integration 31