Configuring An Ldap Client With Yast - Novell LINUX ENTERPRISE DESKTOP 11 - SECURITY GUIDE 17-03-2009 Manual

Line 2 gives a brief description of the attribute with DESC. The corresponding RFC on
which the definition is based is also mentioned here. SUP in line 3 indicates a superor-
dinate attribute type to which this attribute belongs.
The definition of the object class organizationalUnit begins in line 4, like in
the definition of the attribute, with an OID and the name of the object class. Line 5
features a brief description of the object class. Line 6, with its entry SUP top, indicates
that this object class is not subordinate to another object class. Line 7, starting with
MUST, lists all attribute types that must be used in conjunction with an object of the
type organizationalUnit. Line 8, starting with MAY, lists all attribute types that
are permitted in conjunction with this object class.
A very good introduction to the use of Schemas can be found in the documentation of
OpenLDAP. When installed, find it in /usr/share/doc/packages/openldap2/
admin-guide/index.html.
4.3 Configuring an LDAP Client with
YaST
YaST includes a module to set up LDAP-based user management. If you did not enable
this feature during the installation, start the module by selecting Network Services >
LDAP Client. YaST automatically enables any PAM and NSS related changes as required
by LDAP and installs the necessary files. Simply connect your client to the server and
let YaST manage users over LDAP. This basic setup is described in Section 4.3.1,
"Configuring Basic Settings" (page 35).
Use the YaST LDAP client to further configure the YaST group and user configuration
modules. This includes manipulating the default settings for new users and groups and
the number and nature of the attributes assigned to a user or group. LDAP user manage-
ment allows you to assign far more and different attributes to users and groups than
traditional user or group management solutions. This is described in Section 4.3.2,
"Configuring the YaST Group and User Administration Modules" (page 38).
34 Security Guide