R. Saeks July ’06 - 5 -
Directory Setup
There are three ways in which it is possible to allow users to login with network-based accounts to OS X machines.
One of those is to use existing unused attributes on the user object in the Directory Service and populate them as
necessary. Using this method can pose problems later on if these attributes are needed for new functionality due to
a new feature applied to the directory. Another method is to employ static and dynamic LDAP mappings on the
client. This method can be used for some mappings, however any changes require modifying the Directory Access
configuration on the client to reflect the changes. The final way is to extend the schema. This is the preferred way
as it adds additional attributes to the schema, which are utilized only for the reason they were added. In addition,
this allows for a more manageable environment.
Using this method will ensure the potential issue of duplicate schema extensions does not occur. Also, it is much
easier to change a setting on a user account in a directory service rather than having to change static mappings on
each client. The strongest benefit of extending the network schema is to allow for a more managed environment.
Prior to the setup on the client, there are necessary object-classes that must be added to eDirectory. These
attributes can be broken down into several main areas. The object classes covered here fall into the following
categories:
User Attributes
✻
Group Attributes
♦
Mount Attributes
✻
Computer Attributes
♦
Machine List Attributes
♦
Configuration Attributes
♦
Additional classes and extensions may be utilized, however are not covered in this guide.
The needed attributes for a user to authenticate are Mount and User Attributes. The Mount attributes tell the
operating system where, and how, to mount the network-based location that will serve as the home for the user.
The User attributes are what OS X uses to authenticate, and identify, the user. Attributes in this group include the
Users Home Directory, password, name, unique ID, Group ID, and other settings relating to an individual.
✻
These object-classes are required for user authentication and login
♦
These object-classes are used for Management settings and policies.
Comentarios a estos manuales