activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gturner <george.tur...@lmco.com>
Subject CLIENT_CERT using TransportConfiguration
Date Mon, 23 May 2016 15:30:59 GMT
I am using the following code:

            Map<String, Object> connectionParams = new HashMap<>();
            connectionParams.put(TransportConstants.HOST_PROP_NAME,
"socmission");
            connectionParams.put(TransportConstants.PORT_PROP_NAME, "8443");
            connectionParams.put(TransportConstants.SSL_ENABLED_PROP_NAME,
"true");
           
connectionParams.put(TransportConstants.HTTP_UPGRADE_ENABLED_PROP_NAME,
"true");
           
connectionParams.put(TransportConstants.HTTP_UPGRADE_ENDPOINT_PROP_NAME,
"https-acceptor");
            TransportConfiguration transportConfiguration = new
TransportConfiguration(
               
"org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnectorFactory",
connectionParams);
            ConnectionFactory cf =
ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.TOPIC_CF,
transportConfiguration);
            Connection connection = cf.createConnection();
            connection.start();
            session = connection.createSession(false,
Session.AUTO_ACKNOWLEDGE);
            Topic t = (Topic) ctx.lookup(topicJndi);


But in order to connect SSL, the only option is to set the system keystore
option.  Is there any option like an SSLContext that would allow me to set
the client certificate in memory instead of writing it out to file to pass
to the system variable?



--
View this message in context: http://activemq.2283324.n4.nabble.com/CLIENT-CERT-using-TransportConfiguration-tp4712258.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message