JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Administration: Naming and Directory Services     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information


Part I About Naming and Directory Services

1.  Naming and Directory Services (Overview)

2.  Name Service Switch (Overview)

3.  Managing DNS (Tasks)

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)

7.  Administering NIS (Tasks)

8.  NIS Troubleshooting

Part III LDAP Naming Services

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)

12.  Setting Up LDAP Clients (Tasks)

13.  LDAP Troubleshooting (Reference)

14.  LDAP Naming Service (Reference)

Blank Checklists for Configuring LDAP

LDAP Commands

General LDAP Tools

LDAP Tools Requiring LDAP Naming Services

Example pam_conf File Using the pam_ldap Module for Account Management

IETF Schemas for LDAP

RFC 2307bis Network Information Service Schema

Mail Alias Schema

Directory User Agent Profile (DUAProfile) Schema

Oracle Solaris Schemas

Projects Schema

Role-Based Access Control and Execution Profile Schema

Internet Print Protocol Information for LDAP

Internet Print Protocol Attributes

Internet Print Protocol ObjectClasses

Printer Attributes

Sun Printer ObjectClasses

Generic Directory Server Requirements for LDAP

Default Filters Used by LDAP Naming Services

15.  Transitioning From NIS to LDAP (Tasks)



Generic Directory Server Requirements for LDAP

To support LDAP clients, all servers must support the LDAP v3 protocol and compound naming and auxiliary object classes. In addition, at least one of the following controls must be supported.

If an LDAP client is using the pam_unix_* modules, the server must support storing passwords in UNIX crypt format.

If an LDAP client is using TLS, the server must support SSL or TLS.

If an LDAP client is using sasl/GSSAPI, the server must support SASL, GSSAPI, Kerberos 5 authentication. Support for GSS encryption over the wire is optional.