268
OES 2 SP3: Planning and Implementation Guide
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:
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 269
.
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
“Assigning the Common Proxy to Existing Services” on
page 269
.
Service
Reason
Archive and Version Services
This service uses the installing administrator as in the past.
Novell AFP
The need for an AFP proxy user has been eliminated in OES 2
SP3 due to a new NMAS method used for client authentication.
Novell Samba
Samba proxy password requirements are not a good fit with the
Common Proxy user.
Novell Storage Services
This requires full rights to administer NSS and continues to require
a system-named user with a system-generated password.
Summary of Contents for OPEN ENTERPRISE SERVER - CONVERSION GUIDE 12-2010
Page 12: ...12 OES 2 SP3 Planning and Implementation Guide...
Page 24: ...24 OES 2 SP3 Planning and Implementation Guide...
Page 50: ...50 OES 2 SP3 Planning and Implementation Guide...
Page 74: ...74 OES 2 SP3 Planning and Implementation Guide...
Page 78: ...78 OES 2 SP3 Planning and Implementation Guide...
Page 80: ...80 OES 2 SP3 Planning and Implementation Guide...
Page 96: ...96 OES 2 SP3 Planning and Implementation Guide...
Page 146: ...146 OES 2 SP3 Planning and Implementation Guide...
Page 176: ...176 OES 2 SP3 Planning and Implementation Guide...
Page 210: ...210 OES 2 SP3 Planning and Implementation Guide...
Page 218: ...218 OES 2 SP3 Planning and Implementation Guide...
Page 226: ...226 OES 2 SP3 Planning and Implementation Guide...
Page 234: ...234 OES 2 SP3 Planning and Implementation Guide...
Page 236: ...236 OES 2 SP3 Planning and Implementation Guide...
Page 244: ...244 OES 2 SP3 Planning and Implementation Guide...
Page 246: ...246 OES 2 SP3 Planning and Implementation Guide...
Page 250: ...250 OES 2 SP3 Planning and Implementation Guide...
Page 254: ...254 OES 2 SP3 Planning and Implementation Guide...
Page 258: ...258 OES 2 SP3 Planning and Implementation Guide...
Page 284: ...284 OES 2 SP3 Planning and Implementation Guide...
Page 286: ...286 OES 2 SP3 Planning and Implementation Guide...
Page 294: ...294 OES 2 SP3 Planning and Implementation Guide...