The attached document covers the configuration of SSL Acceptors in SonicMQ 7.5.1 for the purpose of encrypting messages between the JMS client and the Sonic Broker. The step-by-step instructions walk through each of the steps, including generating a certificate request to applying for a Public and Private key pair from VeriSign and then installing and configuring the SSL certificate to your Sonic Server. This example uses VeriSign for demonstration purposes, but other Certifying Authorities exist, and you should check with your customer for a preferred vendor. Some of the well known CA's are:

  • VeriSign
  • Thawte
  • Entrust

Progress clients need SSL because...

  • Client has an online store or accepts online orders and credit cards.
  • Client's business partners log in to confidential information on an extranet.
  • Client has distributed offices that share confidential information over an intranet.
  • Client processes sensitive data such as address, birth date, Social Security Numbers, license or ID numbers.
  • Client needs to comply with privacy and security requirements.
  • Client values privacy and expect partners to trust them.

The step-by-step instructions for how to cover the following topics:

  1. Generate a Certificate Signing Request (CSR)
  2. Request a certificate from a Certificate Authority (CA)
  3. Installing and Configuring the Certificates in Sonic
  4. Configuring an SSL Acceptor
  5. Testing an SSL Acceptor
  6. Securing Routed Messages
  7. Using Client Authentication
  8. Certificate File Types
  9. Encryption Cipher Suties and Sonic
  10. Chaining Certificates
  11. Troubleshooting

NOTE: The Sonic Certificate Manager discussed in this paper has been deprecated and no longer ships with Sonic 8.x.  The same result can be achieved with OpenSSL (  Most Linux distributions ship OpenSSL, for Windows check here:

Setting up a SSL acceptor in Sonic 8 is docuemtned here:

Implementing SSL Acceptors (Screen Shots).pdf

Implementinng SSL Acceptors with SonicMQ.pdf