Hello all, I don't know if these messages are even being seen because I haven't received any response. However, if anyone does see this and is interested, I have figured out the solution to my problem.
I'd be happy to share if anyone responds to this email. Thanks, Frank On Tue, Nov 8, 2022 at 2:37 PM Frank Crow <fjcrow2...@gmail.com> wrote: > Hello, > > I've also tried an alternative approach. I have defined an SSL Context > bean like this: > > [image: image.png] > > But when I try to point the SSLContext attribute to it like this: > > [image: image.png] > > It tells me: > > "Cannot convert value of type 'java.lang.String' to required type > 'javax.net.ssl.SSLContext' for property 'SSLContext': no matching editors > or conversion strategy found" > > How do I point that property to my FIPS SSL Context bean? > > Thanks, > Frank > > > > On Tue, Nov 8, 2022 at 2:04 PM Frank Crow <fjcrow2...@gmail.com> wrote: > >> Hello, >> >> I'm trying to configure TLS/SSL connectors using ActiveMQ 5.16.5 under >> FIPS. I'm using the following SSL Context configuration: >> >> [image: image.png] >> >> When I do that, an exception is thrown at startup which boils down to: >> >> "Transport Connector could not be registered in JMX: java.io.IOException: >> no such algorithm: TLS for provider SunPKCS11-NSS-FIPS" >> >> Apparently the algorithm is controlled by the *protocol *attribute but >> I've been unable to figure out any value that works. I've tried "TLSv1", >> "TLSv1.1", "TLSv1.2", and even "SSLv3" but none has worked. >> >> Can anyone tell me how to get that to work? Is there a different >> *sslContext >> *that can work under FIPS? >> >> >> Thanks, >> -- >> Frank >> > > > -- > Frank > -- Frank
