[jira] [Resolved] (AMQNET-469) Add support for self-signed broker certificates

["Timothy Bish (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQNET-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQNET-469.
---------------------------------

    Resolution: Fixed
      Assignee: Timothy Bish  (was: Jim Gomes)

Fix applied on trunk.  

> Add support for self-signed broker certificates
> -----------------------------------------------
>
>                 Key: AMQNET-469
>                 URL: https://issues.apache.org/jira/browse/AMQNET-469
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>            Reporter: Christoffer Sawicki
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 1.7.0
>
>         Attachments: add-support-for-self-signed-broker-certificates.patch
>
>
> ActiveMQ NMS does currently not support self-signed broker certificates since doing so requires a custom System.Net.Security.RemoteCertificateValidationCallback AFAIK.
> The attached patch adds the new configuration option "brokerCertFilename" to SslTransport(Factory) that when used enables an alternative RemoteCertificateValidationCallback that supports self-signed certificates through direct certificate comparison.
> Note #1: The patch does currently not include an automated test, but I'm willing to work on that if that's the only obstacle for integration.
> Note #2: Apache.NMS.Stomp could/should be patched the same way.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)