That's great that you figured out your issue.

There are some potential gotchas for outbound HTTPS connections. You'll want to ensure that the CA that signed the certificate of the HTTPS endpoint is provisioned as trusted by Breeze. You'll also need to ensure that you use com.avaya.collaboration.ssl.util.SSLUtilityFactory to create an SSLContext that is initialized with the Breeze trusted certs / identity cert. You shouldl probably specifically select TLS 1.2.

We've made some nice enhancements in this area in more recent releases:
- Protocol version defaults to System Manager global setting
- Listener to be notified of certificate changes. Without this you'll need to either create a new Security Context every time, periodically refresh it or redeploy your service after updating certificates.

You may want to look at the sample service that we put into the Breeze 3.4 SDK that illustrates doing outbound HTTPS.

It is http only.

In that case, it should be pretty straightforward! Let us know if you run into problems. Have a great weekend.