Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 albarak@cisco.com does not designate 216.139.250.139 as permitted sender)
Date: Sun, 2 Dec 2012 05:16:37 -0800 (PST)
From: Alon <albarak@cisco.com>
To: dev@activemq.apache.org
Message-ID: <1354454197312-4660069.post@n4.nabble.com>
Subject: Replacing the server and client sockets in ActiveMQ
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

I'd like to replace the sockets in Active MQ 5.7 (server and clients) to be
FIPS compliant (using NSS-JSS sockets)

For the server (broker) sockets i override the createSslTransportServer
method of SslBrokerService and use my own SslTransportFactory. 

For the client side i registered my SslTransportFactory by using 
TransportFactory.registerTransportFactory("ssl",new
MYSslTransportFactory());

All seems to be working fine. ActiveMQ Brokers and listeners use the NSS-JSS
sockets successfully.
Is this the right approach for replacing the SSL sockets in ActiveMQ?

Thanks,
Alon


--
View this message in context: http://activemq.2283324.n4.nabble.com/Replacing-the-server-and-client-sockets-in-ActiveMQ-tp4660069.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.