[
https://issues.apache.org/activemq/browse/AMQNET-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58116#action_58116
]
Timothy Bish commented on AMQNET-239:
-------------------------------------
Update the SslTransport:
To run with the default broker certificate or any other non-valid broker
certificate the client must set the transport.acceptInvalidBrokerCert=true.
The client can be configured to supply a specific Client cert now if the broker
is configured to require client Authentication and the user wants to use a
client Certificate not in their default Key location.
> Add support for SSL to NMS/Stomp
> --------------------------------
>
> Key: AMQNET-239
> URL: https://issues.apache.org/activemq/browse/AMQNET-239
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ, NMS, Stomp
> Affects Versions: 1.2.0
> Reporter: Andreas Ländle
> Assignee: Timothy Bish
> Fix For: 1.3.0
>
>
> As far as i can see there is still no support for SSL in NMS. I guess that
> there is a demand to secure communication between client and broker (e.g. in
> a highly distributed environment where client and broker are connected via
> the public internet).
> So my wish is a possibility to secure my communication between the client and
> the broker using NMS.
> Are there any capabilities i have missed?
> I think the same issue has been disused in august 2008
> (http://old.nabble.com/NMS-ssl-support-td19047073.html)
> Best regards,
> Andreas Ländle
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
