| Skip Navigation Links | |
| Exit Print View | |
|
Working With Naming and Directory Services in Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Working With Naming and Directory Services in Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
Part I About Naming and Directory Services
1. Naming and Directory Services (Overview)
2. Name Service Switch (Overview)
4. Setting Up Oracle Solaris Active Directory Clients (Tasks)
Part II NIS Setup and Administration
5. Network Information Service (Overview)
6. Setting Up and Configuring NIS (Tasks)
9. Introduction to LDAP Naming Services (Overview)
10. Planning Requirements for LDAP Naming Services (Tasks)
11. Setting Up Oracle Directory Server Enterprise Edition With LDAP Clients (Tasks)
Configuring Oracle Directory Server Enterprise Edition by Using the idsconfig Command
Creating a Checklist Based on Your Server Installation
Using Service Search Descriptors to Modify Client Access to Various Services
Setting Up SSDs by Using the idsconfig Command
How to Configure Oracle Directory Server Enterprise Edition by Using the idsconfig Command
Specifying Group Memberships by Using the Member Attribute
Populating the Directory Server With Additional Profiles
How to Populate the Directory Server With Additional Profiles by Using the ldapclient Command
Configuring the Directory Server to Enable Account Management
For Clients That Use the pam_ldap Module
For Clients That Use the pam_unix_* Modules
12. Setting Up LDAP Clients (Tasks)
13. LDAP Troubleshooting (Reference)
14. LDAP Naming Service (Reference)
Note - Before populating the directory server with data, you must configure the server to store passwords in UNIX Crypt format if you are using the pam_unix_* modules. If you are using pam_ldap, you can store passwords in any format. For more information about setting the password in UNIX crypt format, see the Oracle Directory Server Enterprise Edition documents.
ldapaddent reads from the standard input (that being an /etc/filename like passwd) and places this data to the container associated with the service. Client configuration determines how the data will be written by default.
# ldapaddent -D "cn=directory manager" -f /etc/passwd passwd
See the ldapaddent(1M) man page. Also see Chapter 9, Introduction to LDAP Naming Services (Overview) for information about LDAP security and write-access to the directory server.
|