[ 
https://issues.apache.org/jira/browse/QPID-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943255#comment-13943255
 ] 

ASF subversion and git services commented on QPID-5634:
-------------------------------------------------------

Commit 1579986 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1579986 ]

QPID-5634: [Java Broker] Remove support for AccessPlugins at the level of the 
virtualhost. Introduce supports for ACLs rules that include virtualhost 
predicate.

> [Java Broker] Allow ACL rules to express virtual host predicates / remove 
> support for AccessPlugins at vhost level
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-5634
>                 URL: https://issues.apache.org/jira/browse/QPID-5634
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>         Attachments: QPID-5634.tar.bz2
>
>
> Currently, the Java Broker supports a hierarchy of AccessPlugins, with the 
> ability to assign different plugins at the broker and individual virtual host 
> levels.  
> This structure does not fit well with the Broker's overall model.  As a 
> consequence, it is only possible to assign an access plugin at the Broker 
> level through the management APIs.  Assigning a access plugin to a virtual 
> host is not (cleanly) possible.  (The user needs to set a hidden vhost 
> attribute "security.acl" with a value that points to a file).
> It has been decided to remove support for AccessPlugins at the VirtualHost 
> level and change the ACLs expressible at the Broker level to include 
> predicates in terms of the virtual host name. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to