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
. . .
Where:
comment ldapclientd ignores any line beginning with a # delimiter.
section Each section is configured by setting=value information underneath. The section
name must be enclosed by brackets ([ ]) as delimiters. Valid section names are:
• StartOnBoot
• general
• passwd
• group
• netgroup
1
• uiddn
• domain_pwd
• domain_grp
• automount
1
setting
This will be different for each section.
value Depending on the setting, this can be yes, no, or number.
Section Details
Within a section, the following syntax applies:
[StartOnBoot] Determines if ldapclientd starts automatically when the system boots.
enable=<yes|no>
By default, this is enabled after LDAP-UX has been configured by the
LDAP-UX setup program /opt/ldapux/config/setup.
[general]
Any cache setting defined here will be used as the default setting for all
caches (passwd, group, netgroup, uiddn, domain_pwd,
domain_grp, automount, automountmap and dynamic_group).
The cache_size setting defined here will be used for all caches except
dynamic_group.
max_conn=<2-500>
The maximum number of connections ldapclientd can establish to
the directory server (or multiple servers when in a multi-domain
environment. The default value is 20.
connection_ttl=<1-2147483647>
The number of seconds before an inactive connection to the directory
server is brought down and cleaned up. The default value is 120.
num_threads=<1-100>
The number of client request handling threads in ldapclientd. The
default value is 10.
socket_cleanup_time=<10-2147483647>
The interval, in seconds, before the next attempt to clean up the socket
files created by any LDAP-UX client applications that were terminated
abnormally. The default value is 300.
cache_cleanup_time=<1-300>
The interval, in seconds, between the times when ldapclientd
identifies and cleans up stale cache entries. The default value is 10.
1. LDAP-UX using Windows 2000 or 2003 Active Directory Server does not support netgroup , automount and
publickey service data.
94 Administering LDAP-UX Client Services