LDAP-UX Client Services B.04.00 Release Notes

LDAP-UX Client Services Release Notes
LDAP-UX Client Services Overview
Chapter 1 5
controls must be migrated manually. The NIS+ migration scripts
support migration of the following NIS+ service data to an LDAP
directory server:
— groups
— password
— hosts
— services
— rpc
— netgroup
— protocols
— networks
— autofs
— publickey
— user-defined map
Migration scripts are provided to ease the task of importing your
NIS+ data into the LDAP directory. See Chapter 3, “Command and
Tool Reference” in NIS+ to LDAP Migration Guide for a complete
description of the NIS+ to LDAP migration scripts, what they do, and
how to use them.
NIS+ to LDAP migration scripts are used to migrate NIS+ service
data from the NIS+ server to Netscape Directory Server for HP-UX.
These scripts can not be used to migrate service data to the Windows
2000/2003 Active Directory Server.
• Support for SASL/GSSAPI authentication
This release includes support for the GSSAPI SASL authentication
method for Kerberos v5. For this release, LDAP-UX Client Services
only supports SASL/GSSAPI authentication for Microsoft Windows
2000 or 2003 Active Directory Server. This feature is only for proxy
user authentication for the name service subsystem. Host, service or
other principals may be used for the LDAP-UX proxy identity. You
can configure a user, service or host principal using
ldap_proxy_config or use Kerberos keytab file without configuring
proxy. Because SASL/GSSAPI is only used for proxy authentication,
user authentication to a Windows domain should still be configured