Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <20315367.174381295912683248.JavaMail.jira@thor>
Date: Mon, 24 Jan 2011 18:44:43 -0500 (EST)
From: "Arthur Naseef (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-3154) unable to implement custom
 broker-to-broker authorization
In-Reply-To: <12393369.174281295912563396.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arthur Naseef updated AMQ-3154:
-------------------------------

    Attachment: pre_add_broker.patch

Patch which adds a "preAddBroker()" method to BrokerFilter which is designed specifically to secure broker-to-broker connections.

If an exception is thrown by the method, the TransportConnection shuts down.


> unable to implement custom broker-to-broker authorization
> ---------------------------------------------------------
>
>                 Key: AMQ-3154
>                 URL: https://issues.apache.org/jira/browse/AMQ-3154
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>            Reporter: Arthur Naseef
>         Attachments: pre_add_broker.patch
>
>
> Ran into the following issues preventing a custom Broker-To-Broker authentication implementation:
>   - BrokerFilter's addBroker() can not be used to secure a connection:
>       - for duplex connections, it is never called on the initial conneciton
>       - even if addBroker() throws an exception, it does not deny access (it does not close the connection nor prevent other functioning)
>       - addBroker() does not have direct access to the ConnectionContext, nor any other means for the BrokerFilter to access SSL certificates on the SSL transport
>   - BrokerFilter's addConnection() can not be used to secure a connection:
>        - there is no way to distinguish broker connections from clients
> Other approaches were considered, but lead to dead-ends.
> It seems the optimal solution would use the existing addBroker() method.
> A patch will be provided that adds a new method specifically for securing Broker-To-Broker connections.

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