...
Info | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Example - Retrieving the values from the Platform Container
if aliases are used in the keystore, you can use this for retrieving the value of the alias used by the Platform certificate.
|
Info | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Example - Configuring keystore properties
If aliases are used in the keystore, you can use this to configure the value of the alias.
|
...
There are two methods that you can use to make the client/server certificates available on all containers.
Copy the keystore file that was created in TLS Standard Setup from the Platform Container to each of the Execution Containers. The target path is specified by the property
pico.rcp.tls.keystore
.Create a keystore and key pair on each Execution Container, then export and import the certficates. The certificate from the Platform Container must be exported to all Execution Containers. The certificates from the Execution Containers must be exported to the Platform Container.
Run the following command to export a certificate:Code Block language text $ keytool -keystore <keystore file> -export -rfc -alias <alias_name> -file <certificate filename>
Info title Example - Exporting a certificate Code Block language text theme Eclipse $ keytool -keystore $MZ_HOME/keys/container.keys -export -rfc -alias platform -file $MZ_HOME/keys/platform.pem
Run the following command to import a certificate:
Code Block language text $ keytool -import -alias <alias_name> -file <certificate_file_name> -keystore <keystore file> -keypass <password> -storepass <password>
Info title Example - Importing a certificate Enable client authentication by setting the property
pico.rcp.tls.require_clientauth
totrue
.
...