[
https://issues.apache.org/jira/browse/ARTEMIS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280606#comment-17280606
]
ASF subversion and git services commented on ARTEMIS-33:
--------------------------------------------------------
Commit 0bedb3048a1fcdd0e2604d2341842967e8fab628 in activemq-artemis's branch
refs/heads/master from Christoph Läubrich
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=0bedb30 ]
ARTEMIS-33 Generic integration with SASL Frameworks
This adds the opportunity to register new SASL schemes via the default
java service-loader mechanism.
Implementors have to provide an implementation of the ServerSASLFactory
that is responsible for providing instances of the actual scheme.
> Generic integration with SASL Frameworks
> ----------------------------------------
>
> Key: ARTEMIS-33
> URL: https://issues.apache.org/jira/browse/ARTEMIS-33
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 1.0.0
> Reporter: Clebert Suconic
> Priority: Critical
> Fix For: unscheduled
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
