LDAP-UX Client Services B.04.00.03 Release Notes

LDAP-UX Client Services Release Notes
Limitations in NIS/LDAP Gateway
Chapter 1 29
Limitations in NIS/LDAP Gateway
The following are limitations in this version of the NIS/LDAP Gateway.
• Crypt Passwords
The NIS/LDAP Gateway product requires that user passwords be
stored in the directory server in the same format as stored in an
/etc/passwd file. This is known as “Unix Crypt” format. If your
directory server does not understand the {crypt} data type, you can
still use the NIS/LDAP Gateway server. However, these users will
not be able to authenticate to the directory server. One side effect is
that users will not be able to change their own passwords (although a
directory administrator could accomplish this on a user’s behalf.)
Also, other LDAP enabled applications may not work correctly.
• Modifying Data in the Directory
You cannot use the chfn(1) and chsh(1) and passwd(1) commands to
modify data in the directory.
• NIS and NIS/LDAP Gateway
You cannot run an NIS server (ypserv) and an NIS/LDAP Gateway
server (ypldapd) simultaneously on the same system.
• Shadow Passwords Not Supported
You must set the hide_passwords parameter to “no” in the
ypldapd.conf file because shadow passwords are not supported. See
Installing and Administering NIS/LDAP Gateway for details.
• Use Preloaded Maps instead of ypall_caching
You should use the preload_maps parameter to preload maps into
the cache instead of ypall_caching. Use of ypall_caching can
cause a performance bottleneck in the ypldapd server. For more
information, see “Caching” in Installing and Administering
NIS/LDAP Gateway.
• Unsupported Configuration Parameters
The dns_lookups, hide_passwords, and loadmodule configuration
parameters described in Installing and Administering NIS/LDAP
Gateway are not supported in this release of the NIS/LDAP Gateway.