You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2013/11/20 15:25:35 UTC

[jira] [Closed] (QPIDJMS-7) add support for providing SSL configuration other than the JVM default

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

Robbie Gemmell closed QPIDJMS-7.
--------------------------------

    Resolution: Invalid

Changed my mind on leaving this open, closing since it is probably better to raise a new JIRA than discuss two different clients on the same one.

> add support for providing SSL configuration other than the JVM default
> ----------------------------------------------------------------------
>
>                 Key: QPIDJMS-7
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-7
>             Project: Qpid JMS
>          Issue Type: Improvement
>            Reporter: mrich
>
> Provide a mechanism for supplying SSL parameters (e.g. keystore information) to the JMS AMQP 1.0 client at a per connection/factory level.
> Currently, in {{org.apache.qpid.amqp_1_0.client.Connection}} the default {{SSLSocketFactory}} is used, which only picks up the default SSL information provided by either the Java options or setting the system properties.
> More details and the origin of this discussion can be found on the mailing list thread: http://qpid.2158936.n2.nabble.com/Specifying-SSL-information-in-URL-for-AMQP-1-0-tp7598974.html



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org