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
# LDAP-UX does not support netgroup with Windows 2000 Active
# Directory Server.
#
[netgroup]
enable=yes
[uiddn]
enable=yes
[domain_pwd]
enable=yes
[domain_grp]
enable =yes
[automount]
enable =yes
[automountMap]
enable=yes
Integrating with Trusted Mode
This section describes features and limitations, PAM configuration changes and configuration
parameter for integrating LDAP-UX with Trusted Mode.
Overview
Starting with LDAP-UX Client Services B.03.30, the product supports coexistence with Trusted
Mode. This means that local-based accounts can benefit from the Trusted Mode security policies
while LDAP-based accounts benefit from the security policies offered by the LDAP server. This
release of LDAP-UX provides extensive password and account policies, and also enables
LDAP-based and local-based accounts to be audited on the Trusted Mode.
The coexistence of LDAP-UX and Trusted Mode supports certain security features, but also has
limitations and usage requirements that you need to be aware of. For detailed information, see
“Features and Limitations” (page 100).
Features and Limitations
This subsection describes features and limitations of integrating LDAP-UX with Trusted Mode.
Auditing
Integrating LDAP-UX with Trusted Mode enables accounts stored in the LDAP directory to login
to a local host and to be audited on the Trusted Mode. The following describes the auditing
features and limitations. To use these security features, you must enable the audit subsystem on
the Trusted Mode local host:
• Auditing of both LDAP-based and local-based (/etc/passwd) accounts is possible. By default,
auditing is disabled for all LDAP-based accounts. However, you can use the audusr
(option-a or -d) command to alter the auditing flag for individual LDAP-based account.
• For LDAP-based accounts that are not yet known to the system, you can configure an initial
setting for the auditing flag. You can configure this flag such that when an account becomes
known to the system for the first time, auditing for that account is immediately enabled or
disabled. This flag is defined as the initial_ts_auditing parameter in the
/etc/opt/ldapux/ldapux_client.conf file.
• You must manage Trusted Mode attributes for all accounts on each host. Trusted Mode
attributes for LDAP-based accounts are not stored in the LDAP directory server. For example,
enabling auditing for an account on host A does not enable auditing on host B.
100 Administering LDAP-UX Client Services