[
https://issues.apache.org/jira/browse/QPID-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861400#action_12861400
]
Rajith Attapattu commented on QPID-2541:
----------------------------------------
Excellent !
I agree that both brokers needs to have the groups mechanism pluggable.
However we also need to think about how these groups will correspond to the
users handled via the authentication mechanism.
Here are some questions.
1. If we use LDAP, unix file or active directory, is that only used to manage
the groups?
will they be also used with authentication via the SASL EXTERNAL mechanism?
2. If we are not going to use the above mechanisms for authentication, then how
do propose to tie in them?
(I'd question the value of using them for just managing groups, but perhaps
I may have missed something)
The authentication and authorization mechanisms work hand in hand and any
grouping has to be thought in the context of both.
> Separate Group an ACL configuration and make group sources pluggable
> --------------------------------------------------------------------
>
> Key: QPID-2541
> URL: https://issues.apache.org/jira/browse/QPID-2541
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Reporter: Andrew Kennedy
> Fix For: 0.7
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
