Novell IMANAGER 2.7.3, Руководство администратора

Страница: 110 / 114

110 Novell iManager 2.7.3 Administration Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
cd j2sdk1.5.0_11\bin
3
Import the certificate into the keystore with the keytool, executing the following keytool
commands (platform specific):
Š
NetWare
keytool -import -alias [ alias_name ] -file
[ full_path ]\trustedrootcert.der -keystore
sys:java\lib\security\cacerts
Š Windows
keytool -import -alias [ alias_name ] -file
[ full_path ]\trustedrootcert.der -keystore
[ full_path ]\jre\lib\security\cacerts
Š
Linux
keytool -import -alias [ alias_name ] -file [ full_path ]/
trustedrootcert.der -keystore [ full_path ]/jre/lib/security/cacerts
Replace alias_name with a unique name for this certificate and make sure you include the full
path to trustedrootcert.der and cacerts.
The last path in the command specifies the keystore location. This varies from system to
system because it is based on where iManager is installed. The following are the examples of
default locations for iManager on Windows and Linux:
On Windows:
C:\Program Files\Novell\jre\lib\security\cacerts
On Linux:
/usr/lib/jvm/ <java-1_4_2-sun-1.4.2.17> /jre/bin/keytool
4 Enter
changeit
for the keystore password.
5
Click Yes to trust this certificate.
NOTE: This process must be repeated for each eDirectory tree you will be accessing with
iManager. If LDAP has been configured to use a certificate not signed by the tree’s Organizational
CA, you must import that certificate’s Trusted Root. This is necessary, for example, if LDAP is
configured to use a VeriSign*-signed certificate.
A.2 Self-Signed Certificates
iManager includes a temporary, self-signed certificate that you use when installing iManager on any
platform except NetWare. It has an expiration date of one year. For more information, see “
Self-
Signed Certificates ” in the iManager 2.7 Installation Guide .
A.3 iManager Authorized Users and Groups
Authorized Users and Groups are those that iManager permits to perform its various administrative
tasks. For more information about specifying and configuring Authorized Users and Groups, see
“Authorized Users and Groups” on page 72 .
Authorized Users and Groups data is stored in the
configiman.properties
file, which must be
secured to prevent unauthorized modification. To do this, modify the access controls for
configman.properties
to restrict those users authorized to manually edit the file.