LDAP-UX Client Services B.04.00.03 Release Notes

LDAP-UX Client Services Release Notes
Limitations in LDAP-UX Client Services
Chapter 120
Limitations in LDAP-UX Client Services
The following are limitations in this version of the LDAP-UX Client
Services.
/etc/pam.conf
HP delivers two PAM example configuration files, /etc/pam.ldap and
/etc/pam.ldap.trusted, in this release. You need to configure
/etc/pam.conf properly for LDAP-UX to work as expected. When you
integrate LDAP-UX Client Services with the Netscape Directory Server,
if your system is in the standard mode, the pam_unix library must be
defined before pam_ldap as they are in the /etc/pam.ldap file. If your
system is in the trusted mode, the pam_ldap library must be defined
before pam_unix, and both libraries must be specified as "required"
under "Session management". See Appendix C, “Sample
/etc/pam.ldap.trusted File”, on LDAP-UX Client Services
Administrator’s Guide for details.
LDAP Directory Interoperability
The LDAP-UX product has been certified under the OpenGroup’s works
with LDAP 2000 branding.
LDAP-UX has been designed to work with any directory server that can
support the RFC 2307 schema or similar syntactic schema (such as the
Microsoft Services For Unix 3.0 schema). The LDAP-UX product requires
the "Configuration Profile" schema, which is defined at the IETF drafts
web site http://www.ietf.org/ID.html.
This draft is currently published as draft-joslin-config-schema-07.txt
(which will likely be replaced by a future draft revision or RFC). The
"Configuration Profile" schema will be automatically installed on
directory servers that support online modification of the subschema
subentry.
The following list of directories have been tested or minimally verified.
• Netscape Directory Server for HP-UX 6.x - Fully tested and
supported