[
https://issues.apache.org/jira/browse/QPID-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071121#comment-15071121
]
ASF subversion and git services commented on QPID-6917:
-------------------------------------------------------
Commit 1721639 from [email protected] in branch 'java/trunk'
[ https://svn.apache.org/r1721639 ]
QPID-6917: Make Web Management Console SASL mechanisms plaggable and convert
existing SASL implementations into plaggable classes
> Make web SASL pluggable in web management UI
> --------------------------------------------
>
> Key: QPID-6917
> URL: https://issues.apache.org/jira/browse/QPID-6917
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Alex Rudyy
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-6917-Make-Web-Management-Console-SASL-mechanism.patch
>
>
> Currently the web management hard codes the sasl mechanisms it knows about
> with an if/then/else ladder. We want to make the sasl mechanism pluggable.
> The client will know the sasl mechanisms that the server supports during the
> initial /sasl request. The client side should try to load the sasl
> implementation from a well known location URL. If the sasl client mechanism
> is found the implementation (which will meet an agreed interface - probably
> based on the Java Sasl Client design), will be used. If the sasl mechanism
> doesn't exist, the client should fall through to the next mechanism.
> It will be possible to increase the SASL mechanisms supported by a WMC by
> dropping in a web fragment JAR containing another SASL js implementation.
> We need to decide how the client will chose its preferred mechanism.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
