Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 13 Nov 2014 01:18:25 +0000 (UTC)
From: "clebert suconic (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12754936.1415841142000.486490.1415841505824@Atlassian.JIRA>
In-Reply-To: <JIRA.12754936.1415841142000@Atlassian.JIRA>
References: <JIRA.12754936.1415841142000@Atlassian.JIRA>
 <JIRA.12754936.1415841142821@arcas>
Subject: [jira] [Updated] (ACTIVEMQ6-33) Generic integration with SASL
 Frameworks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

clebert suconic updated ACTIVEMQ6-33:
-------------------------------------
    Fix Version/s: 6.1.0
          Summary: Generic integration with SASL Frameworks  (was: Generic integration with SASL)

> Generic integration with SASL Frameworks
> ----------------------------------------
>
>                 Key: ACTIVEMQ6-33
>                 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-33
>             Project: Apache ActiveMQ 6
>          Issue Type: New Feature
>            Reporter: clebert suconic
>             Fix For: 6.1.0
>
>
> Right now we are bound to User/Password or anonymous on SASL.
> We should use some framework that would allow SASL integration with a bigger number of possibilities.
> We should investigate options from the JDK for this... or if there is any other framework available.
> I believe this only affects AMQP, but as part of this issue we should investigate if there is any interest extending SASL into any other protocol.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)