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
/opt/ldapux/bin/ldapclientd <-f| -k| -L| -h| -r>
Command Options
Refer to the ldapclientdman page(s) for option information.
Diagnostics
By default, errors are logged into syslog if the system log is enabled in the LDAP-UX client
startup configuration file /etc/opt/ldapux/ldapux_client.conf. Errors occurring before
ldapclientd forks into a daemon process leave an error message directly on the screen.
The following diagnostic messages may be issued:
Message: Already running.
Meaning: An attempt was made to start an LDAP client daemon when one was already running.
Message: Cache daemon is not running (or running but not ready).
Meaning: This message can mean several things:
• Attempted to use the control option features of ldapclientd when no ldapclientd
daemon process was running, to control.
• Attempted to start or control ldapclientdwithout superuser privilege.
• The ldapclientd daemon process is too busy with other requests to respond at this time.
Try again later.
Message: Problem reading configuration file.
Meaning: The/etc/opt/ldapux/ldapclientd.conf file is missing or has a syntax error.
If the problem is with its syntax, the error message will be accompanied by a line showing exactly
where it could not recognize the syntax, or where it found a setting which is out of range.
CAUTION: Whenever the system is rebooted, ldapclientdlaunches if [StartOnBoot] has
the parameter enabled=yes in the file /etc/opt/ldapux/ldapclientd.conf (the
ldapclientdconfiguration file). Downloading profiles takes time, depending on the server's
response time and the number of profiles listed in the LDAP-UX startup
file,/etc/opt/ldapux/ldapux_client.conf.
The ldapclientd.conf Configuration File
The file ldapclientd.confis the configuration file for/opt/ldapux/bin/ldapclientd,
the LDAP client daemon. Refer to the previous section for more information about the daemon.
Missing Settings
ldapclientd uses the default values for any settings which are not specified in the
configuration file.
Configuration File Syntax
# comment
[section]
setting=value
setting=value
. . .
[section]
setting=value
setting=value
Using the LDAP-UX Client Daemon 93