Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Date: Thu, 15 Oct 2015 22:44:12 -0400 (EDT)
From: Justin Bertram <jbertram@apache.com>
To: users@activemq.apache.org
Message-ID: <628182777.32475144.1444963452439.JavaMail.zimbra@redhat.com>
In-Reply-To: <1444924897125-4703003.post@n4.nabble.com>
References: <1444841282120-4702960.post@n4.nabble.com>
 <1640516219.31946425.1444850113251.JavaMail.zimbra@redhat.com>
 <1444902321770-4702988.post@n4.nabble.com>
 <1444924897125-4703003.post@n4.nabble.com>
Subject: Re: Artemis - Certificate Security
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: Artemis - Certificate Security
Thread-Index: rTm2wA5Kxt3ULrr8XU1BUaLHNggomQ==

I haven't looked into it in too much details but whatever is done should be done far enough into the broker that it works for all (or at least most) of the protocols.  I think you'd probably need to create a new extension of org.apache.activemq.artemis.spi.core.security.ActiveMQSecurityManager.


Justin

----- Original Message -----
From: "slew77" <stephen.lewis77@yahoo.co.uk>
To: users@activemq.apache.org
Sent: Thursday, October 15, 2015 11:01:37 AM
Subject: Re: Artemis - Certificate Security

So based on ActiveMQ 5, I want to grab the certificate from the
ConnectionInfo.transportContext.

I can get the certificate array in ActiveMQChannelHandler.channelRead, but
means I have to propagate it using bufferReceived.

Then in OpenWireConnection.bufferReceived I can setTransportContext on the
ConnectionInfo object, which is the unmarshalled buffer.

OK approach or did you have another plan in mind?


--
View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Certificate-Security-tp4702960p4703003.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.