I think that setting your own SSLContext will be the only way to achieve that. It's certainly one of the reasons that ability was added.
If you are starting out, you might want to look at e.g https://github.com/vert-x3/vertx-proton/ or https://github.com/vert-x3/vertx-amqp-client/ instead, which each build a think layer on each other and on proton-j in its original protocol-engine usage model (rather than the reactor bits) and leveraging Netty for IO and TLS etc. On Fri, 26 Feb 2021 at 17:07, Beekwilder, Norm <norm.beekwil...@tridium.com> wrote: > > Hi, > I'm using Proton-J 0.33.6 for a Java 8 client application. I have a > security requirement to restrict which cipher suites are used when > connecting. However, other than using > Proton.sslDomain().setSslContext(SSLContext) I'm having trouble figuring out > how to configure the SSL connection. I would prefer a programmatic solution > if one exists but am willing to investigate other options too. > Thanks > Norm --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
