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)
Prerequisites to LDAP Client Setup
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
The LDAP client service is managed by using the Service Management Facility. For an overview of SMF, refer to Chapter 18, Managing Services (Overview), in System Administration Guide: Basic Administration. Also refer to the svcadm(1M) and svcs(1) man pages for more details.
Administrative actions on this service, such as enabling, disabling, or restarting, can be performed by using the svcadm command.
Tip - Temporarily disabling a service by using the -t option provides some protection for the service configuration. If the service is disabled with the -t option, the original settings would be restored for the service after a reboot. If the service is disabled without -t, the service will remain disabled after reboot.
The Fault Managed Resource Identifier (FMRI) for the LDAP client service is svc:/network/ldap/client:<instance>.
You can query the status of the LDAP client and ldap_cachemgr by using the svcs command.
Example of svcs command and output.
# svcs \*ldap\* STATE STIME FMRI online 15:43:46 svc:/network/ldap/client:default
Example of svcs -l command and output. To get the output shown below, you must use the instance name in the FMRI.
# svcs -l network/ldap/client:default fmri svc:/network/ldap/client:default enabled true state online next_state none restarter svc:/system/svc/restarter:default contract_id 1598 dependency require_all/none file://localhost/var/ldap/ldap_client_file (-) dependency require_all/none svc:/network/initial (online) dependency require_all/none svc:/system/filesystem/minimal (online)
You can check a daemon's presence by using the ps command.
# ps -e | grep slapd root 23320 1 0 Aug 27 ? 16:30 ./ns-slapd -D \ /usr/iplanet/ds5/slapd-lastrev -i /usr/iplanet/ds5/slapd-lastrev/ root 25367 25353 0 15:35:19 pts/1 0:00 grep slapd
Note - Do not use the -f option with ps because this option attempts to translate user IDs to names, which causes more naming service lookups that might not succeed.