Non-default TLS certificates
- Last Updated: November 5, 2025
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
The Unified Broker Framework has the “certStorePath” TLS property to specify
the path to the trusted certificate store which is the root certificate for the certificate
authority that was used to sign the server certificate. Servers using this customized
certificate can connect clients instantiated with a matching certificate specified using
-certstorepath command line parameter of the client.
However, in a Probroker configuration, responsibility for spawning a TLS or a non-TLS DataServer servers rests with the Probroker based on whether it was instantiated with a TLS or a non-TLS command line parameter. A TLS-enabled ProBroker can include the following startup parameters to customize the use of certificates and key stores by brokers.
| Parameter | Description |
|---|---|
|
|
The path to the trusted certificate store.The root certificate for the certificate authority that was used to sign the server certificate should be specified by this path. |
|
|
Specifies the key store location. |
|
|
Specifies the alias set for a private/public key. If this parameter is not provided, the server certificate alias that is provided by OpenEdge is used. |
|
|
Specifies the encoded password set for the alias of
the private/public-key to access the server Private Key / Digital Certificate key
store entry. You can use the OpenEdge provided genpassword utility
for encoding your passwords.For more information on the |
|
|