You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2008/05/14 17:37:46 UTC

[jira] Resolved: (AMQ-1724) Allow ssl context configuration through spring/xbean

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

Hiram Chirino resolved AMQ-1724.
--------------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

Implemented the feature with a more concise xml notation and also avoided using static singleton to hold the ssl configuration.  This allows you to configure each broker with a different ssl keystore even if there are multiple brokers in 1 JVM.

example:

{code}
  <broker>

    <sslContext>
      <sslContext 
      		keyStore="server.keystore" keyStorePassword="password"
      		trustStore="client.keystore" trustStorePassword="password"/>
    </sslContext>
    
    <transportConnectors>
      <transportConnector uri="ssl://localhost:61616" />
    </transportConnectors>
    
  </broker>
{code}

> Allow ssl context configuration through spring/xbean
> ----------------------------------------------------
>
>                 Key: AMQ-1724
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1724
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Gary Tully
>             Fix For: 5.2.0
>
>         Attachments: AMQ-1724.patch
>
>
> amq ssl works with the javax.net.ssl system properties and can be configured via SslBroker without the system properties as shown in AMQ-1665. It would be better if it was possible to configure via spring or xbean.

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