You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jamie goodyear (JIRA)" <ji...@apache.org> on 2018/12/07 18:21:00 UTC

[jira] [Resolved] (AMQCPP-619) Support for SSL wilcard certificate

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

Jamie goodyear resolved AMQCPP-619.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.10.0

Thank you Francois Godin for the patch.

This update will be included in a future 3.10.0 release.

> Support for SSL wilcard certificate
> -----------------------------------
>
>                 Key: AMQCPP-619
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-619
>             Project: ActiveMQ C++ Client
>          Issue Type: New Feature
>    Affects Versions: 3.9.4
>            Reporter: Francois Godin
>            Assignee: Jamie goodyear
>            Priority: Major
>             Fix For: 3.10.0
>
>         Attachments: amqcpp-619.patch, sslCertificateWildcard.patch
>
>
> SSL certificate can contain wildcard in the hostname. For example, the certificate URL "*.proxy.app.com" should match the following address:
> * 1.proxy.app.com
> * 2.proxy.app.com
> Sadly, ActiveMQ-CPP simply compare the two values and thus does not accept such certificates.
> The Openssl page https://wiki.openssl.org/index.php/Hostname_validation describe some possible implementation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)