
1. Change to the certificate keystore directory. cd /opt/mobilitygw-2.1/
server/default/data
2. Delete the default Avaya 3100 Mobile Communicator Administration Server
keystore.
rm admin-ssl-keystore
If the keystore does not exist, you see the message rm: cannot Istat 'ssl-
keystore': No such file directory
3. Generate the Avaya 3100 Mobile Communicator Administration Server keystore
and private key.
/usr/java/jdk1.6.0_03/bin/keytool -genkey -validity
<valDays> -alias smog-ssl -keyalg RSA -keystore ssl-keystore
4. When prompted, enter the Avaya 3100 Mobile Communicator Administration Server
keystore password. You should choose a strong password.
5. When prompted for a first and last name, enter the Common Name for the Avaya
3100 Mobile Communicator Administration Server. Use a fully qualified domain
name (FQDN), for example, mg.domain.com.
Important:
The same FQDN must be entered on all mobile clients that employ SSL/TLS.
6. If required by your CA, enter the optional information (for example, organization or
city) when prompted.
7. When prompted to enter the key password for SMOG-SSL, press Return to use
the keystore password specified in 4 on page 92.
8. Change ownership of the Avaya 3100 Mobile Communicator Administration Server
keystore from root to mobility with the following two commands:
chown mobility:mobility admin-ssl-keystore
chmod 755 admin-ssl-keystore
9. Generate the certificate signing request for the Avaya 3100 Mobile Communicator
Administration Server.
/usr/java/jdk1.6.0_03/bin/keytool -certreq -keyalg RSA -
alias smog-ssl -file mgcertreq.csr -keystore admin-ssl-
keystore
10. Update the HTTPS certificate password for the Avaya 3100 Mobile Communicator
Administration Server with the password specified in
4 on page 92 using the
following command:
Server certificate management
92 Administration and Security October 2010
Kommentare zu diesen Handbüchern