Introduction
Overview of LDAP-UX Client Services
directory, as shown below. LDAP adds greater scalability, interoperability with other applications and platforms, and less network traffic from replica updates.
Figure 1-2 | A Simplified LDAP-UX Client Services Environment |
| | | | Updates | | | | | | | |
| | | | | | | | | | |
| | | | | LDAP Directory | | |
| | LDAP Directory |
| | Server | | | | Server Replica | | |
| | |
| | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
LDAP Requests
LDAP-UX client | | LDAP-UX client |
| | |
LDAP-UX Client Services supports the following name service data: passwd, groups, hosts, rpc, services, networks, protocols, publickeys, automount, netgroup. See the LDAP-UX Integration B.04.00 Release Notes for any additional supported services.
How LDAP-UX Client Services Works
LDAP-UX Client Services works by leveraging the authentication mechanism provided in the Pluggable Authentication Module, or PAM, and the naming services provided by the Name Service Switch, or NSS. See pam(3), pam.conf(4), and Managing Systems and Workgroups at http://docs.hp.com/hpux/os for information on PAM. For information on NSS, see switch(4) and “Configuring the Name Service Switch” in Installing and Administering NFS Services at http://docs.hp.com/hpux/communications/#NFS.
These extensible mechanisms allow new authentication methods and new name services to be installed and used without changing the underlying HP-UX commands. And, by supporting the PAM architecture, the HP-UX client becomes truly integrated in the LDAP environment. The PAM_LDAP library allows the HP-UX system to use the LDAP directory as a trusted server for authentication. This means that