You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/02/14 16:43:05 UTC

[jira] Commented: (QPID-6) Need to make SSL options configurable

    [ https://issues.apache.org/jira/browse/QPID-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473125 ] 

Martin Ritchie commented on QPID-6:
-----------------------------------

The changes to Main haven't been replicated in cluster.Main. Wasn't that hard to replicate changes but noted that trying to use SSL wouldn't have worked on cluster code as it never used the ssl handler. The cluster code has become somewhat outdated.

Commited at revsion 507584

> Need to make SSL options configurable
> -------------------------------------
>
>                 Key: QPID-6
>                 URL: https://issues.apache.org/jira/browse/QPID-6
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Martin Ritchie
>             Fix For: M2
>
>         Attachments: config_ssl_broker.patch, qpid_ssl.tar.gz
>
>
> In both the client and broker, the SSL support lacks the ability to configure basically anything. 
> We need to be able to allow the user/administration to configure the certificate, keystore and so on. 
> On the broker, look at org.amqp.blaze.server.protocol.AMQPFastProtocolHandler line 97. From there trace into the org.amqp.blaze.ssl.BogusSSLContextFactory which is the class that hardcodes stuff in a way that is very useful for a dev environment! 
> Basically the task in this jira is to make this whole area fully configurable.  
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.