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

NOTE: The userPassword attribute is mapped to *NULL*
to prevent passwords from being returned for increased
security and to prevent PAM_UNIX from authenticating
users in the LDAP directory. Mapping to *NULL* or any
other nonexistent attribute means do not return anything.
authenticationMethod
is how the client binds to the directory. The value can be
simple indicating bind using a user name and password.
If this attribute has no value, simple is the default.
bindTimeLimit
is how long, in seconds, the client should wait to bind before
aborting. 0 (zero) means no time limit. If this attribute has
no value, the default is no time limit.
credentialLevel
is the identity clients use when binding to the directory. The
value must be one of the following: proxy, anonymous, or
proxy anonymous. proxy means use the configured proxy
user. anonymous means use anonymous access. proxy
anonymous means use the configured proxy user and if
that fails, bind anonymously. If this attribute has no value,
anonymous is the default.
defaultSearchBase
is the base DN where clients can find user and group
information, for example DC=cup,DC=hp,DC=com. This
attribute must have a value.
defaultServerList
is a list of one or more host IP addresses and optional port
numbers where LDAP directory servers are running. Each
host is searched in the order given. The LDAP-UX client
searches the servers until it finds one that responds,
defaultServerList is used only if the preferedServerList
attribute has no value, or if none of the specified servers in
preferredServerList responds the client request. If neither
defaultServerList nor preferredServerList specifies a host,
the LDAP-UX client does not try to connect to any LDAP
directory server. See preferredServerList below.
For example, 15.10.120.150:350 is the host at IP address
15.10.120.150 using port number 350. When specifying
multiple hosts, each host:port entry must be separated by a
space.
followReferrals
specifies whether or not referrals should be followed. If the
entry is 0 (zero), referrals will not be followed. If the attribute
has no value or any other numeric value, referrals will be
followed.
preferredServerList
is a list of one or more host IP addresses and optional port
numbers where LDAP directory servers are running. Each
host is searched in the order given. If this attribute has no
value, or if none of the specified servers satisfies the client's
request, the defaultServerList is used. See
defaultServerList for more information.
For example, 15.13.128.145:250 is the host at IP address
15.13.128.145 using port number 250. When specifying
multiple hosts, each host:port entry must be separated by a
space.
profileTTL
is the recommended time interval before refreshing the
cached configuration profile.
searchTimeLimit
is how long, in seconds, a client should wait for directory
searches before aborting. 0 (zero) means no time limit. If this
attribute has no value, the default is no time limit.
160 LDAP-UX Client Services Object Classes