Novell OPEN ENTERPRISE SERVER - PLANNING AND IMPLEMENTATION GUIDE 12-2010 Implementation Manual page 268


Novell Cluster Services

Linux User Management (proxy user is optional)
Services that Cannot Leverage the Common Proxy User
The following services that use proxy users do not leverage the Common Proxy user for the reasons
listed:
Service
Archive and Version Services
Novell AFP
Novell Samba
Novell Storage Services
Can a Common Proxy User Service Multiple Servers?
No.
The common proxy user is designed and configured to be the common proxy for the OES services
on a single server. Each subsequent new server needs a separate and distinct proxy created for its
services.
Can I Change the Common Proxy User Name and Context?
Yes.
However, best practice suggests that eDirectory object names and locations within the tree reflect
the object purpose and scope of influence or function. For this reason, the default Common Proxy
User name is OESCommonProxy_hostname, where hostname is the name of the OES server being
installed, and the default eDirectory context is the same as for the server for which the common
proxy is created.
IMPORTANT: If you specify a different context from the server, the Organizational Unit that you
specify must already exist in eDirectory. Otherwise, the server installation will fail, and you'll need
to start over.
Can I Assign the Common Proxy User After Services Are Installed?
Yes. See "Assigning the Common Proxy to Existing Services" on page
What About Upgraded Servers Using a Common Proxy?
You can change the services running on an OES 2 server that has been upgraded to OES 2 SP3 to
leverage a Common Proxy user. See
page 269.
268 OES 2 SP3: Planning and Implementation Guide
Reason
This service uses the installing administrator as in the past.
The need for an AFP proxy user has been eliminated in OES 2
SP3 due to a new NMAS method used for client authentication.
Samba proxy password requirements are not a good fit with the
Common Proxy user.
This requires full rights to administer NSS and continues to require
a system-named user with a system-generated password.
"Assigning the Common Proxy to Existing Services" on
269.