| 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)
12. Setting Up LDAP Clients (Tasks)
13. LDAP Troubleshooting (Reference)
14. LDAP Naming Service (Reference)
15. Transitioning From NIS to LDAP (Tasks)
NIS-to-LDAP Tools and the Service Management Facility
NIS-to-LDAP Audience Assumptions
When Not to Use the NIS-to-LDAP Service
Effects of the NIS-to-LDAP Service on Users
NIS-to-LDAP Transition Terminology
NIS-to-LDAP Commands, Files, and Maps
Transitioning From NIS to LDAP (Task Map)
Setting Up the NIS-to-LDAP Service
How to Set Up the N2L Service With Standard Mappings
How to Set Up the N2L Service With Custom or Nonstandard Mappings
NIS-to-LDAP Best Practices With Oracle Directory Server Enterprise Edition
Creating Virtual List View Indexes With Oracle Directory Server Enterprise Edition
VLVs for Custom and Nonstandard Maps
Avoiding Server Timeouts With Oracle Directory Server Enterprise Edition
Avoiding Buffer Overruns With Oracle Directory Server Enterprise Edition
Debugging the NISLDAPmapping File
How to Revert to Maps Based on Old Source Files
Before implementing the N2L service, you must check or complete the following items.
Make sure that the system is set up as a working traditional NIS server before running the inityp2l script to enable N2L mode.
Configure the LDAP directory server on your system.
Oracle Directory Server Enterprise Edition and compatible versions of directory servers offered by Oracle, are supported with the NIS-to-LDAP migration tools. If you use Oracle Directory Server Enterprise Edition, configure the server by using the idsconfig command before you set up the N2L service. For more information about idsconfig, see Chapter 11, Setting Up Oracle Directory Server Enterprise Edition With LDAP Clients (Tasks) and the idsconfig(1M) man page.
Other (third-party) LDAP servers might work with the N2L service, but they are not supported by Oracle. If you are using an LDAP server other than the Oracle Directory Server Enterprise Edition or compatible Oracle servers, you must manually configure the server to support RFC 2307bis, RFC 4876, or their successors' schemas before you set up the N2L service.
Use files before dns for the config/host property.
Ensure that the addresses of the N2L master server and the LDAP server are present in the hosts file on the N2L master server.
An alternative solution is to list the LDAP server address, not its host name, in ypserv. This means that the LDAP server address is listed in another place, so changing the address of either the LDAP server or the N2L master server requires additional file modifications.
|