LDAP-UX Client Services B.04.00.02 Release Notes

LDAP-UX Client Services Release Notes
Known Problems and Workarounds
Chapter 120
Known Problems and Workarounds
For LDAP-UX Client Services
This section describes all currently known problems with the LDAP-UX
Client Services product.
• Active Directory Server
If password expires, the user cannot log into HP-UX clients. The
administrator will have to reset the password or the user will have to
log into the Windows 2000 or 2003 system to reset password before
he can log into HP-UX machines.
If the account option “user must change password at next
logon” is set, then on 11i v1, the user can not log into the HP-UX
machine even if the password has not expired and is still valid. 11i
v2 doesn’t have this limitation.
• Proxy User Configuration
If you change the authentication method from SIMPLE (with or
without SSL) to SASL DIGEST-MD5 (with or without SSL), or vice
versa, the proxy user will become invalid if you don’t update the
proxy user during setup.
The workaround is to remove the /etc/opt/ldapux/pcred file, then
run the command, /opt/ldapux/config/ldap_proxy_config -i,
to reconfigure it.
Netscape Directory Server 6.11 (and lower versions) does not support
expired passwords for DIGEST-MD5.
• Netgroups
— The NIS optimization maps 'byuser' and 'byhost' are not utilized
— Each triple is stored as single string
— Each triple must be enclosed by parentheses, e.g. "(machine,
user, domain)" is a valid triple, while "machine, user, domain" is
not
• Hosts