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

Number of Group Members Returned
With dynamic membership support, as with regular (static) group membership support, the
number of group members for a specific group returned by
getgrnam()/getgrgid()/getgrent() on an HP-UX system is limited by internal buffer
sizes. On HP-UX 11i v1 and v2 systems, the buffer size is 7296 bytes for 32bit applications and
10496 bytes for 64bit applications. This limitation is mainly impacted by the size of each member
name. For detailed description, refer to the Preparing your Directory for LDAP-UX Integration white
paper under the "Account and Group Management" collection available at the following web
site:
http://docs.hp.com/en/internet.html
During the login process, information for getting group members is not requested. The login
time will not be affected by processing group members.
Number of Groups Returned for a Specific User
When ldap is configured in the /etc/nsswitch.conf file as a data repository for the group
service (see nsswitch.conf(4)), if an LDAP user logs into an HP-UX system, LDAP-UX is
involved to return all groups that the user belongs to. The login application (e.g. login) initializes
the user's group access based on the group information returned by LDAP-UX.
Information for getting groups that a specific user belongs to is requested by LDAP-UX during
login via initgroups(). LDAP-UX returns at most 20 groups for a system limit on HP-UX 11i
v1 and v2 systems. If the user belongs to more than 20 groups, only the first 20 groups are
returned. The support of dynamic groups does not change the system limitation.
Depending on how you configure groups, if those 20 groups happens to be the last entries of
thousands of dynamic groups, the login time could be long and performance could be impacted.
Based on the configuration of memberUid attribute mappings, LDAP-UX may return static
and/or dynamic groups. The first memberUid mapped attribute determines if LDAP-UX returns
static or dynamic groups first. If the first memberUid mapped attribute is a static group attribute
(such as memberUid or member). LDAP-UX returns static groups first. If there are less than 20
static groups, LDAP-UX then returns dynamic groups for the rest groups. On other hand, if the
first memberUid mapped attribute is a dynamic group attribute, msDS-AzLDAPQuery, LDAP-UX
returns dynamic groups first. If there are less than 20 dynamic groups, LDAP-UX then returns
static groups for the rest groups.
For example, if a user belongs to 8 static groups and 20 dynamic groups, and you map memberUid
to memberUid msDS-AzLDAPQuery , LDAP-UX will return 8 static groups and 12 dynamic
groups. If you map memberUid to msDS-AzLDAPQuery memberUid, LDAP-UX will return 20
dynamic groups without any static groups.
Number of Group Members Returned 87