Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Sun, 9 Feb 2014 14:48:23 -0800 (PST)
From: artnaseef <art@artnaseef.com>
To: users@activemq.apache.org
Message-ID: <62D4FE9E-A4EA-4406-A392-2A39EE4749BD@artnaseef.com>
In-Reply-To: <1391985468926-4677667.post@n4.nabble.com>
References: <1391985468926-4677667.post@n4.nabble.com>
Subject: Re: NMS SSL Client Settings
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_12627_9530297.1391986103537"

------=_Part_12627_9530297.1391986103537
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Are you looking for howto info?

To make server cert checking work, the client must trust the server's cert. That means either get a server (broker) cert signed by a known trusted Certificate Authority (CA) or add the CA that did sign the cert to the client's trusted CA list. 

Sent from my iPhone

> On Feb 9, 2014, at 3:38 PM, "pwalter [via ActiveMQ]" <ml-node+s2283324n4677667h25@n4.nabble.com> wrote:
> 
> 
> From article by Tim Bish I was able to use the following client config settings: 
> ssl://localhost:61617?transport.acceptInvalidBrokerCert=true 
> 
> Currently it won't work without the transport setting.. 
> I need to make this more secure (i.e. not accept invalid Broker) 
> 
> Thanks 
> 
> If you reply to this email, your message will be added to the discussion below:
> http://activemq.2283324.n4.nabble.com/NMS-SSL-Client-Settings-tp4677667.html
> To start a new topic under ActiveMQ - User, email ml-node+s2283324n2341805h3@n4.nabble.com 
> To unsubscribe from ActiveMQ - User, click here.
> NAML


--
View this message in context: http://activemq.2283324.n4.nabble.com/NMS-SSL-Client-Settings-tp4677667p4677668.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
------=_Part_12627_9530297.1391986103537--