Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) |
Part I About Naming and Directory Services
1. Naming and Directory Services (Overview)
2. The Name Service Switch (Overview)
Part II DNS Setup and Administration
3. DNS Setup and Administration (Reference)
Part III NIS Setup and Administration
4. Network Information Service (NIS) (Overview)
5. Setting Up and Configuring NIS Service
Part IV LDAP Naming Services Setup and Administration
8. Introduction to LDAP Naming Services (Overview/Reference)
9. LDAP Basic Components and Concepts (Overview)
10. Planning Requirements for LDAP Naming Services (Tasks)
11. Setting Up Sun Java System Directory Server With LDAP Clients (Tasks)
12. Setting Up LDAP Clients (Tasks)
LDAP and the Service Management Facility
Using Profiles to Initialize a Client
How to Initialize a Client Using Profiles
How to Initialize a Client Using Per-User Credentials
How to Initialize a Client Using Proxy Credentials
Enabling Shadow Updating in LDAP
How to Initialize a Client to Enable the Updating of Shadow Data
Initializing a Client Manually
How to Initialize a Client Manually
Modifying a Manual Client Configuration
How to Modify a Manual Configuration
Configuring PAM to Use UNIX policy
Configuring PAM to Use LDAP server_policy
Retrieving LDAP Naming Services Information
Listing All User Entry Attributes
Customizing the LDAP Client Environment
Modifying the nsswitch.conf File for LDAP
13. LDAP Troubleshooting (Reference)
14. LDAP General Reference (Reference)
15. Transitioning From NIS to LDAP (Overview/Tasks)
16. Transitioning From NIS+ to LDAP
A. Solaris 10 Software Updates to DNS, NIS, and LDAP
In order for a Solaris client to use LDAP as a naming service the following needs to be in place.
The client's domain name must be served by the LDAP server
The nsswitch.conf file needs to point to LDAP for the required services
The client needs to be configured with all the given parameters that define its behavior
ldap_cachemgr needs to be running on the client
At least one server for which a client is configured must be up and running
The ldapclient utility is the key to setting up an LDAP client, as it performs all of the above steps, except for starting the server. The rest of this chapter will show examples of how to use the ldapclient utility to set up an LDAP client and use the various other LDAP utilities to get information about, and check the status of, an LDAP client.