[
https://issues.apache.org/jira/browse/ARTEMIS-33?focusedWorklogId=548984&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-548984
]
ASF GitHub Bot logged work on ARTEMIS-33:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Feb/21 06:16
Start Date: 06/Feb/21 06:16
Worklog Time Spent: 10m
Work Description: laeubi commented on pull request #3432:
URL: https://github.com/apache/activemq-artemis/pull/3432#issuecomment-774408418
@gemmellr @gtully I think this can be used as a first step, just one thing I
noticed (but that could be changed later also):
Even though I removed the storage of multiple providers for the same scheme
it might still be valuable to restore this. I noticed that e.g. the java sasl
API do it the way that they (in case of multiple ones) ask them in order and
return the first one returning a non-null client/server object.
We could do a similar thing here, MechanismFinder#getFactory would then
simply return a list of factories.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 548984)
Time Spent: 2h 40m (was: 2.5h)
> 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)
