[ 
https://issues.apache.org/jira/browse/QPID-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-7705:
-----------------------------
    Summary: [Java Broker] Inconsistent ACL behaviour  between various versions 
of Qpid Brokers when 'Unbind' privilege is required  for removal of queue 
bindings on temporary queue  deletion  (was: [Java Broker] Inconsistent ACL 
behaviour  between various versions of Qpid Brokers when 'Unbind' privilege is 
required  for removal of queue bindings on temporary queue queue deletion)

> [Java Broker] Inconsistent ACL behaviour  between various versions of Qpid 
> Brokers when 'Unbind' privilege is required  for removal of queue bindings on 
> temporary queue  deletion
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7705
>                 URL: https://issues.apache.org/jira/browse/QPID-7705
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.32, qpid-java-6.0, qpid-java-6.1, 
> qpid-java-broker-7.0.0
>            Reporter: Alex Rudyy
>
> With 0.32 Java Broker ACL implementation a temporary queue is allowed to be 
> deleted  by the owner (for example using JMS {{Session#deleteQueue()}}) 
> without the need for explicit grant of UNBIND privilege to the user. In Qpid 
> Broker versions 6.0 and 6.1 the UNBIND privilege is required for queue 
> deletion because as part of queue deletions all existing bindings are removed 
> and if UNBIND is not granter the binding deletion fails causing queue 
> deletion failure. In the trunk version (7.0) the UNBIND is not required ( See 
> QPID-7703) for temporary queue deletion. We need to fix  this ACL 
> inconsistency.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to