Configuring Broker cipher suite and cryptographic protocols.
1. To configure a the UBroker to only accept secure protocols and allow a restricted set of Cipher Suites update the
<DLC>/properties/ubroker.properties with the following Environment Variables under the UBroker's Environment section, where entries are comma separated:
For instance, test the client by configuring the server to only allow a restricted set of GCM Cipher Suites SHA256 available since TLS 1.2:
[Environment.asbroker1]PSC_SSLSERVER_PROTOCOLS=TLSv1.2
PSC_SSLSERVER_CIPHERS=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2562. The SSL algorithm list to use in arbitrating an
SSL Session with the
SSL client can be defined with the
sslAlgorithms parameter:
[UBroker.AS.asbroker1]
...
environment=asbroker1 sslAlgorithms=AES128-SHA256:AES256-SHA256:DHE-RSA-AES128-SHA256:AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA256:ADH-AES128-GCM-SHA256:ADH-AES256-SHA256To use the 256 bit AES Ciphers, it is necessary to install
JCE Unlimited Strength Jurisdiction Policy Files:
The following Articles provide useful quick reference and additional information:
Cryptographic Protocols and Ciphers supported by OpenEdge are published since the OpenEdge 11.6 version: