You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/06/08 10:44:21 UTC
[jira] [Updated] (QPID-6907) Add ability to restrict read in ACLs
[ https://issues.apache.org/jira/browse/QPID-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-6907:
-----------------------------
Fix Version/s: (was: Future)
qpid-java-6.2
> Add ability to restrict read in ACLs
> ------------------------------------
>
> Key: QPID-6907
> URL: https://issues.apache.org/jira/browse/QPID-6907
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-6.2
>
>
> Currently the ACL mechanism has no way to restrict what a management user can see. If the user can authenticate, then they are entitled to see all the objects beneath Broker. There is no way to express user A should have management permission to read below virtual host X.
> ACLs do have an ACCESS permission, be this is used to govern connections to virtual hosts for messaging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org