Overview of NIS+ to LDAP Migration
Comparing LDAP and NIS+ Information Sharing
LDAP-UX Client Services improves on this configuration information sharing. User, group, and other network operating system configuration information can be integrated with other identity information in other organization-wide applications. The account and configuration information is stored in an LDAP directory. Client systems retrieve this shared configuration information across the network from the LDAP directory. In addition, LDAP adds greater scalability, interoperability with other applications and platforms, and less network traffic from replica updates. Figure 1-3 shows a simplified LDAP-UX Client Services Environment.
Figure 1-2 | A Simplified LDAP-UX Client Services Environment |
| | | | | | | | | | |
| | LDAP Directory | | | | | | | | |
| | | | | | | | | |
| | | | LDAP Directory | |
| | Server | | | |
| | | | Server Replica | | |
| | | | | |
user account data
netgroup data
services data Updates automount data
security data
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, printers, netgroup, automount and public key.
How LDAP-UX Client Services Work
LDAP-UX Client Services works by leveraging the authentication mechanism provided in the Pluggable Authentication Module (PAM) and the naming services provided by the Name Service Switch (NSS).