Customizing master domain manager and dynamic agent certificates

Procedure to use customized certificates for communication between master domain manager and dynamic agent

About this task

The procedure explained below is one of several procedures you can perform to achieve the same results and is intended only as an example. In this procedure, it is assumed your certificates have been signed by a Certificate Authority (CA) you created for this purpose. For more information, see Creating a Certificate Authority. For more information about using an external CA or manually modifying all the keystores and key databases, see Replacing Default SSL Certificates with CA Signed Custom Certificates.

To customize the certificates for communication between master domain manager and dynamic agent, perform the following steps:

Procedure

On the master domain manager, generate a self-signed certificate or issue a certificate sign request to a CA and import the certificate into TWSServerKeyFile.jks. For example, you can generate the private key to be used for signing the custom certificate by issuing the following command:
```
openssl genrsa -des3 -out tls.key 2048
```

Create the certificate sign request:

openssl req -new -key tls.key -out tls.csr -config
/usr/Tivoli/TWS/OpenSSL64/1.0.0/bin/openssl.cnf

Send the .csr to the CA:
```
openssl x509 -req -in tls.csr -days 3650
-CA ca.crt -CAkey ca.key -CAcreateserial -out tls.crt
```
Note: If you do not specify the -CAcreateserial parameter, the default certificate validity of 30 days applies.

After receiving back the signed certificate, you can import the custom certificate along with its private key into TWSServerKeyFile.jks, as follows:

Create a single file containing both:
```
cat tls.key tls.crt > tls.tot
```

Export the resulting file to a PKCS12 keystore:

openssl pkcs12 -export -out TWSServerKeyFile.p12 -in tls.tot -name server

Import the PKCS12 keystore into TWSServerKeyFile.jks:

keytool -importkeystore -srckeystore TWSServerKeyFile.p12 -srcstoretype pkcs12
-destkeystore TWSServerKeyFile.jks -deststoretype jks -srcstorepass password
-deststorepass password -srcalias server -destalias server

On the master domain manager, import the CA certificate in the TWSServerTrustFile.jks:
```
keytool -importcert -file ca.crt -keystore TWSServerTrustFile.jks
-alias ca -trustcacerts
```
On the master domain manager, edit the TWA_DATA_DIR/broker/config/BrokerWorkstation.properties file and update the list of authorized Common Names for the dynamic domain manager (broker). Append the Common Name used for the custom certificate to the Broker.AuthorizedCNs property:
```
Broker.AuthorizedCNs=Server;ServerNew;new_CN
```
Run the AgentCertificateDownloader script on the dynamic agent. The script connects to the master domain manager, downloads the certificates in .PEM format (tls.key, tls.crt, ca.crt files), and deploys them to the agent. The certificates must be available on the master domain manager in a specific path. For more information, see Certificates download to dynamic agents - AgentCertificateDownloader script.