LDAP-UX Integration B.04.20 Release Notes (June 2009)

NOTE: Compatibility with features not specified in the base LDAP RFCs is not guaranteed.
Interoperability issues are likely in areas such as schema management and/or password and
account policy evaluation/enforcement.
Supported Name Service Databases
• LDAP-UX Client Services using Netscape/Red Hat Directory Server supports the following
name services data:
— passwd
— group
— netgroup
— services
— rpc
— hosts
— networks
— automount
— publickey
— protocols
— user-defined maps
• LDAP-UX Client Services using Windows 2003/2003 R2/2008 Active Directory Server does
not support netgroup and publickey service data.
• LDAP-UX Client Services using Windows 2003/2003 R2/2008 Active Directory Server currently
supports hosts, protocols, networks, rpc, automount and services in a single domain. It only
supports passwd and group service data in multiple domains.
• The LDAP-UX Client Services daemon, /opt/ldapux/bin/ldapclientd, caches only passwd, group,
netgroup, automount service data.
Duplicated Data Entries in ADS Multiple Domains
To better integrate with HP-UX, it is highly recommended that you maintain unique user names
and uid numbers in the forest, or undesired behaviors may occur. For example:
• If an ADS Global Catalog server is configured to retrieve data from remote domains,
LDAP-UX won’t return data if there are duplicate entries in any remote domains
• For users having the same user name in multiple domains, LDAP-UX may return user data
from a different domain if the original domain controller fails
• A user may not be able to change their password if his/her uid number is not unique in the
forest
Limitations of Printer Configurator
• The new LDAP printer schema based on /etc/opt/ldapux/schema/RFC3712.xml is imported
into the Netscape/Red Hat Directory Server to create the printer objects.
• The LDAP-UX Client Services only supports the HP LP spooler system, network printers,
and printer servers that support the Line Printer Daemon (LPD) protocol. The printer
configurator does not support local printers.
• In a global management environment, it is hard to determine a default printer for the
individual client system. The LDAP printer configurator treats every printer entry as the
regular printer. The administrator or user is required to manually select a printer as a default
printer for the client system.
Limitations in LDAP-UX Client Services 27