[
https://issues.apache.org/jira/browse/QPID-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860293#action_12860293
]
Rajith Attapattu commented on QPID-2541:
----------------------------------------
Users are under the purview of the authentication mechanism.
We use SASL for that.
Groups in ACL is a convenience mechanism in ACL to allow a bunch of users (or
groups) to be identified together.
As mentioned in the email thread, specifying the groups in the ACL file is just
a convenience method.
By all means we need to allow them to be configured via other sources.
(However having a separate file for specifying groups doesn't really make
sense.)
My preferred option of allowing dynamic provisioning of groups is via QMF as
explained in QPID-2537
What other sources do you have in mind?
> 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:dev-subscr...@qpid.apache.org
