![[16.0.0.3 and later]](../ng_v16003.gif)
Setting up third-party certificates for an existing collective
You can set up third-party certificates for an existing collective.
About this task
To set up third-party certificates for an existing collective, you need to change the keystore and truststore, which are displayed in the following image:

Tip: You can find the keytool utility in your Java™ installation
directory.
Important: All members and controllers must use CA
certificates.
Procedure
- Retrieve one SSL personal certificate for the controller that is signed by a third-party CA. For example, the certificate is available in keystore controller_pers_cert.jks and member_pers_cert.jks.
- Retrieve the signer certificates of both controller personal certificate and member personal certificates. For example, the certificates are available in files controller_signer_cert.cer and member_signer_cert.cer.
- Configure the collective controller side.
- Stop the controller and members.
- Go to the {controller_server_dir}/resources/collective directory.
- Remove the certificates that are in serverIdentity.jks.
- Import the controller personal certificate to the serverIdentity.jks file.
You can use the keytool utility, which is part of JDK.
keytool -importkeystore -srckeystore controller_pers_cert.jks -destkeystore serverIdentity.jks - Remove the signers from collectiveTrust.jks.
- Add the controller and member personal certificate signers to the
collectiveTrust.jks file.
keytool -import -trustcacerts -file controller_signer_cert.cer -keystore collectiveTrust.jks -alias "controllerSignerAlias"keytool -import -trustcacerts -file member_signer_cert.cer -keystore collectiveTrust.jks -alias "MemberSignerAlias" - Go to the {controller_server_dir}/resources/security directory.
- Replace the contents of key.jks with the contents of serveIdentity.jks.
- Replace the contents of trust.jks with collectiveTrust.jks.
- Start the collective controller.
- Configure each collective member side.
- For the member, retrieve a personal certificate that is signed by the member signer certificate. You may use one personal certificate for all members, or create a different certificate for each member. For example, the certificate is available in member_pers_cert.jks.
- Go to {member_server_dir}/resources/collective.
- Remove the certificates in serverIdentity.jks.
- Add the member personal certificate that is signed by the certificate authority to the
serverIdentity.jks file.
keytool -importkeystore -srckeystore member_pers_cert.jks -destkeystore serverIdentity.jks - Remove the signers from collectiveTrust.jks.
- Add the controller certificate signers to the collectiveTrust.jks
file.
keytool -importkeystore -srckeystore member_pers_cert.jks -destkeystore serverIdentity.jks - Replace the contents of key.jks with the contents of serveIdentity.jks.
- Replace the contents of trust.jks and controllerTrust.jks with the contents of the respective trust stores in the controller.
Parent topic:
Setting up collectives with third-party certificates
Setting up collectives with third-party certificates
Tema de tarea
Última actualización: Tuesday, 6 December 2016http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-zos&topic=tagt_wlp_setup_exist_collective
Nombre de archivo:tagt_wlp_setup_exist_collective.html