LDAP-UX Integration B.04.10 Release Notes
Table Of Contents
- LDAP-UX Integration B.04.10 Release Notes
- Table of Contents
- 1 LDAP-UX Integration B.04.10 Release Note
- LDAP-UX Integration Overview
- LDAP-UX Client Services
- What’s New in LDAP-UX Client Services B.04.10
- Known Problems fixed in LDAP-UX Client Services A.04.10
- Compatibility and Installation Requirements for LDAP-UX Client Services
- Installing and Configuring the LDAP-UX Client Services
- Documentation
- Known Problems and Workarounds for LDAP-UX Client Services
- Limitations in LDAP-UX Client Services
- Services
- /etc/pam.conf
- LDAP Directory Interoperability
- Supported Name Service Databases
- Duplicated Data Entries in ADS Multiple Domains
- SSL With Windows 2000 Active Directory Server
- Limitations of Printer Configurator
- Unsupported Commands
- Clear Text Passwords
- Man page for ldapclientd.conf
- LDAP Security Policy Enforcement
- SASL/GSSAPI Profile Download Support
- Changing authentication methods
- Supported Features For Particular Directory Servers
- Additional Limitations with Active Directory
- NIS/LDAP Gateway
• Defect Number JAGaf79435
ldapclientd indefinitely waits for a response from the LDAP server. After submitting a
request to the LDAP server, ldapclientd loops if the LDAP server cannot respond to that
request due to a heavy load on the server, a system hang, a network outrage, etc. To resolve
this problem the ldapclientd daemon drops the connection with the LDAP server after
the "searchtimelimit" is reached
• Defect Number JAGaf81185
32-bit PA-RISC applications with +q3p enabled calling the getpwuid() function fail with
ENOMEM. This problem occurs because q3p-enabled applications cannot be mmap()’ed to
the same file.
• Defect Number JAGaf81363
Memory fault occurs with a 64-bit Perl application. The problem is caused by the
inet_aton() function calling strtok_r() function without specifying the-D_REENTRANT
flag in the corresponding Makefiles.
• Defect Number JAGag25520
The ldapclientd daemon consumes 100% of CPU time when processing a corrupted
request. This problem is caused by ldapclientd using the sprintf() function to build
a search filter. A corrupted message passed to sprintf() does not fit into the buffer. As
a results, sprintf() does not return and consumes 100% of the CPU.
Compatibility and Installation Requirements for LDAP-UX Client Services
This section provides basic instructions for installing and configuring the LDAP-UX Client
Services. Please refer to LDAP-UX Client Services Administrator’s Guide, or LDAP-UX Client Services
with Microsoft Windows Active Directory Administrator’s Guide for complete instructions on how
to install and configure LDAP-UX Client Services
Preparing for Installation
Memory Requirements.
This product has minimal memory and disk requirements. However with the addition of the
ldapclientd caching daemon, additional memory may be required to support very large name
spaces (more than 50,000 users, for example) on very active hosts. The statistics operation
(-S) on ldapclientd can be used to determine memory requirements. See the ldapclientd
man page (section 1M) for more details. Your system should have at least 32 MB of main memory,
and at least 40 megabytes of free disk space under /opt.
Hardware Requirements.
An HP 9000 or HP Integrity (ia64) computer system.
Operating System Requirements.
HP-UX 11i v1, 11i v2 or 11i v3.
Patch Requirements
For 11i v1, HP requires that you install the patch listed in Table 1-1, this table is shown below.
For 11i v2 or v3, no patch is required.
You may use the following command to determine which patches are installed on your system:
/usr/sbin/swlist -l product | grep PH | more
See the swlist(1M) man page for more information.
Patches can be obtained from the HP Electronic Support Center at: http://us-support.external.hp.com/
12 LDAP-UX Integration B.04.10 Release Note