LDAP-UX Client Services B.04.10 with Microsoft Windows Active Directory Server Administrator's Guide

recommended to run the authck -d command when you configure LDAP-UX with Trusted
Mode.
• You cannot use the Trusted Mode management subsystem in SAM to manage LDAP-based
accounts.
• The LDAP repository and /etc/passwd repository must not contain accounts with the same
login name or account number.
• Except for the audit flag, you cannot modify other Trusted Mode properties/policies for
LDAP-based accounts. For example, if you attempt to lock an LDAP-based account by
modifying the Trusted Mode field for that user, it does not prevent that account from logging
in to the host. Instead, you must disable the account on the LDAP server itself. No runtime
warning will be given that the local locking of the account has no effect. It is important that
all system administrators are properly trained, so that administrative locks on accounts have
the desired effect.
Configuration Parameter
LDAP-UX Client Services provides one configuration parameter, initial_ts_auditing,
available for you to configure the initial auditing setting for the LDAP-based account. This
parameter is defined in the /etc/opt/ldapux/ldapux_client.conf file.
SASL GSSAPI Support
LDAP-UX Client Services B.04.00 includes support for the SASL / Generic Security Services
Application Programming Interface (GSSAPI) authentication method for Kerberos v5. Currently,
Kerberos v5 is the only security mechanism that is implemented to work with GSSAPI. For this
release, we provide SASL/GSSAPI authentication method support only for Microsoft Windows
2000 or 2003 Active Directory. We do not provide SASL/GSSAPI authentication method support
for Netscape Directory Server. SASL/GSSAPI authentication is only for proxy user authentication
for the name service subsystem. Host, service or other principles may be used for the LDAP-UX
proxy identity. Because SASL/GSSAPI is only used for proxy authentication, user authentication
to a Windows domain should still be configured using PAM_Kerberos.
For information on the realm, principal, keytab and credential cache definitions used by the
SASL GSSAPI authentication, refer to Configuration Guide For Kerberos Product on HP-UX and
Installing, Configuring and Administering The Kerberos Server on HP-UX 11i at
http://docs.hp.com/hpux/internet.
102 Administering LDAP-UX Client Services