System User and Group Management in OES 2 SP3
269
Are There Important Limitations to Keep in Mind?
Yes.
iFolder must not be configured to use a Common Proxy on a cluster node.
I.3.2 Managing Common Proxy Users
Common proxy users are eDirectory objects and can therefore be managed via iManager. However,
after the initial setup is complete, there should generally be no reason for OES administrators to
directly manage Common Proxy users.
Use the information in the following sections to understand and implement common proxy user
management.
“Always Use LDAP Port 636 to Communicate with eDirectory” on page 269
“Assigning the Common Proxy to Existing Services” on page 269
“Changing Proxy Passwords Automatically” on page 270
Always Use LDAP Port 636 to Communicate with eDirectory
The Common Proxy user management scripts communicate with eDirectory using port 636 only.
See the instructions in “
Installing OES 2 SP3 as a New Installation
” in the
OES 2 SP3: Installation
Guide
).
Assigning the Common Proxy to Existing Services
You can assign the common proxy user to any of the services listed in
“Services That Can Leverage
the Common Proxy User” on page 267
using the
move_to_common_proxy.sh
script on your OES 2
SP3 server. In fact, if you have upgraded from SP2 and the server doesn’t have a common proxy
user associated with it, simply running the script will create and configure the proxy user and assign
the services you specify.
1
In the
/opt/novell/proxymgmt/bin
folder, run the following command:
move_to_common_proxy.sh
service1
,
service2
where the service entries are OES service names.
Example scenario:
You have upgraded server myserver, which is located in o=novell and uses IP address
10.10.10.1, from SP2 to SP3.
The secure LDAP port for the server is 636.
Your eDirectory Admin user FQDN is cn=admin.o=novell.
Your Admin password is 123abc.
You want to create a common proxy user and assign it as the common proxy for the Novell
DNS and DHCP services running on the server.
Therefore, you enter the following commands:
cd /opt/novell/proxymgmt/bin
move_to_common_proxy.sh -d cn=admin.o=novell -w 123abc -i 10.10.10.1 -p
636 -s novell-dhcp,novell-dns
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...
