Creating a new SSL certificate to replace an existing one in a node

When using the -asExistingNode option on the addNode command, you might be adding an existing node to a different machine. The default Secure Sockets Layer (SSL) certificate of the node does not contain the name of the machine the node is located on. In most scenarios, the subject DN of the default certificate does not make a difference. However, you might want to change the default certificate of the node to contain the hostname of the node.

1. Click Security > SSL certificate and key management > Key stores and certificates.
2. Select the NodeDefaultKeyStore of the node you want to change.
3. Under Additional Properties, select Personal certificates.
4. Under the Create pull-down, select Chained Certificate.
5. Enter a certificate and alias name.
   This can be any name you choose as long as the alias does not already exist. It is just a label to identify the certificate in the keystore.
6. Enter a common name.
   This is typically the hostname the node is running on.
7. Optional: Fill in any of the other Subject DN related fields.
   If you want the subject DN to look like the default subjectDN on WebSphere Application Server, then enter:
   • IBM in the Organization field.
   • <cell name>,ou=<node name> in the Organization unit field.
   • Under the Country or region pull-down, select US.
8. You can use the defaults for Root certificate used to sign the certificate, Key Size, and Validity Period or supply your own values.
9. Click Apply.
   Note: You can also create a new chained certificate using the createChainedCertificate command. Read PersonalCertificateCommands command group for the AdminTask object for more information.

   You must now replace the old certificate with the one you just created. The replace certificate option not only replaces the old default certificate with a new one but also replaces any occurrences of the signer of the old certificate with the signer of the new certificate. The configuration is also checked for references to the alias name of the old certificate and replaces it with the alias name of the new certificate. To replace the old certificate with the new one, complete the remaining steps.

10. Click Security > SSL certificate and key management > Key stores and certificates.
11. Select the NodeDefaultKeyStore of the node you want to change.
12. Under Additional Properties, select Personal certificates.
13. Select the default certificate of the node, usually called default.
14. Click Replace.
15. Select the certificate alias name for the certificate you just created from the Replace with pull-down.
16. Click Delete old Certificate after replacement.
17. Click Apply.
    Note: You can also create a new chained certificate using the replaceCertificate command. Read PersonalCertificateCommands command group for the AdminTask object for more information.