Correct - accepting invalid certs is not secure. Your client will connect to any broker using ssl regardless of cert validity in that case.
Note I sm being a little vague because I am not certain of the NMS settings. You want the ssl url without the transport.acceptInvalidBrokerCert=true setting to be secure. Sent from my iPhone > On Feb 9, 2014, at 5:00 PM, "pwalter [via ActiveMQ]" > <ml-node+s2283324n4677670...@n4.nabble.com> wrote: > > Should this work? (removing the transport) with a valid certificate? > From: > ssl://localhost:61617?transport.acceptInvalidBrokerCert=true > TO: > ssl://localhost:61617 > > I'm concerned that the transport.acceptInvalidBrokerCert=true is not "secure" > > > 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-tp4677667p4677670.html > To start a new topic under ActiveMQ - User, email > ml-node+s2283324n234180...@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-tp4677667p4677671.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
