activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From soody <atins...@gmail.com>
Subject Alternatives for deprecated setKeyAndTrustManagers in ActiveMQSSLConnectionFactory
Date Thu, 26 Mar 2009 15:21:33 GMT

We want to use SSL in our client that will be sending messages to ActiveMQ.
But we can't set the trust stores and key stores using System.setProperty(),
as our's is an enterprise application. 

Are there any ways that I can set the trust and key stores, basically the
SSLContext. Currently what we are thinking is that we will be using the
SSLContext.setCurrentSslContext(<will create a context using JSSE and dump
it here>). 

Is there any better approach. Also will be great if we can get anything more
pluggable, s.th that we can use across multiple JMS providers.

Also why is the method setKeyAndTrustManagers  marked as deprecated and what
is the workaround for the same.
-- 
View this message in context: http://www.nabble.com/Alternatives-for-deprecated-setKeyAndTrustManagers-in-ActiveMQSSLConnectionFactory-tp22724170p22724170.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message