Novell OPEN ENTERPRISE SERVER 2 SP2 - ADMINISTRATION, Implementation Manual, Page: 272 / 288

272 OES 2 SP2: Planning and Implementation Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
I.4.2 Service-Specific Proxy Users
Do the following:
1. Create a proxy user in the eDirectory tree for each type of OES service and set the passwords.
Consider naming the user to reflect its purpose. For example, name the AFP proxy user,
afp_proxy_user.
2. Use these proxy users and passwords appropriately for each of the OES services on all OES
servers.
I.4.3 Partition-Wide Proxy Users
Do the following:
1. Create one proxy user object per eDirectory partition in the OES tree, and set the password.
Consider naming the user to reflect its purpose. For example, name the proxy user for the
London regional office, london_office_proxy_user.
2. Use this proxy user and password for configuring all of the OES services on all the OES servers
in that partition.
I.4.4 Server-Wide Proxy User
Do the following:
1. Create one proxy user object per OES server (preferably in the same container as the server)
and set the password
2. Use this proxy user and password as the proxy user for all the services on that particular OES
server.
I.4.5 Individual Proxy User Per-Server-Per-Service
This is the installation default as explained in Table I-6, “Options for Limiting the Number of Proxy
Users,” on page 267 .
I.5 Proxy Users and Domain Services for
Windows
Proxy users are not used in DSfW.
The Services part of the Trusted Computed Base has the rights to read users’ supplemental
credentials for authentication. A separate Kerberos process reads user passwords and performs the
authentication. Another event handler in eDirectory creates the supplemental credentials for the user
whenever the password is changed for that user.
I.6 System Users
SLES and OES create system users on the local Linux system to provide user IDs (uids) to service
processes. These users have rights to local files, such as configuration files.