janylj wrote:
>
> I tried ActiveMQ JNDI support. It seems to me only for testing, because
> the administrative objects are specified in the jndi.properties of client
> machine. There is no centralized place to manage the ConnectionFactory or
> Destination. And we could not control who could acce
It appears that I have to force AMQ to have its JAAS login module use a
JAASCertificateCallbackHandler; at least that's my inference.
Anyhow when I used the following in my activemq.xml:
...things worked i.e. I can see the client cert.
Note the difference between "jaasCertificateAuthenticatio
semog wrote:
>
> So here is my Jabber settings from our Hudson build server:
>
> Jabber ID: hudson-dev
> Password: * (this doesn't really matter)
> Initial group chats: hudsont...@conference.jmsserver
> Server: jmsserver
> Port: 61222
> Expose Presence: true
>
> ActiveMQ is running on
