| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Administration: Naming and Directory Services Oracle Solaris 11 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris Administration: Naming and Directory Services Oracle Solaris 11 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)
How to Add a New NIS User to an NIS Domain
Changing a Map's Master Server
How to Change a Map's Master Server
How to Modify Configuration Files
Modifying and Using /var/yp/Makefile
Changing Makefile Macros/Variables
How to Modify /var/yp/Makefile to Use Specific Databases
How to Modify the Makefile to Delete Databases
Updating and Modifying Existing Maps
How to Update Maps Supplied With the Default Set
Using the cron Command for Map Transfers
Using Shell Scripts With cron and ypxfr
Directly Invoking the ypxfr Command
Using the makedbm Command to Modify a Non-Default Map
Creating New Maps From Text Files
Adding Entries to a File-Based Map
Creating Maps From Standard Input
Modifying Maps Made From Standard Input
Binding to a Specific NIS Server
Setting a Machine's NIS Domain
How to Set a Machine's NIS Domain Name
Using NIS in Conjunction With DNS
How to Configure Machine Host Name and Address Lookup Through NIS and DNS
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)
For security reasons, follow these guidelines.
It is best to limit access to the NIS maps on the master server.
The files used to build the NIS password maps should not contain an entry for root to protect against unauthorized access. To accomplish this, the password files used to build the password maps should have the root entry removed from them and be located in a directory other than the master server's /etc directory. This directory should be secured against unauthorized access.
For example, the master server password input files could be stored in a directory such as /var/yp, or any directory of your choice, as long as the file itself is not a link to another file and is specified in the Makefile. When you use either the Service Management Facility or the ypstart script to start the NIS service, the correct directory option is set according to the configuration specified in your Makefile.
|