You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jonas Lim (JIRA)" <ji...@apache.org> on 2007/02/15 03:59:03 UTC
[jira] Created: (AMQ-1163) bug in reading temp queue using the
tempDestinationAuthorizationEntry feature
bug in reading temp queue using the tempDestinationAuthorizationEntry feature
------------------------------------------------------------------------------
Key: AMQ-1163
URL: https://issues.apache.org/activemq/browse/AMQ-1163
Project: ActiveMQ
Issue Type: Bug
Reporter: Jonas Lim
Assigned To: Jonas Lim
Fix For: 4.2.0
> Folks,
>
> I've been trying to use the tempDestinationAuthorizationEntry feature in 4.2
> and I think I've found a problem. If I set up a consumer of the temp queue
> and add it to the read permission, it always reports that I don't have
> permission to read the queue. However, if I add that consumer to the write
> permission on the queue it works like a charm.
>
> Looking at the source I think I have discovered a bulk copy/paste problem.
> If you look at
> org.apache.activemq.security.AuthorizationBroker.addConsumer() in the source
> trunk, you will see this little piece of code a couple of lines from the top
> of the method:
>
> if(!info.getDestination().isTemporary()) {
> allowedACLs =
> authorizationMap.getReadACLs(info.getDestination());
> }else {
> allowedACLs = authorizationMap.getTempDestinationWriteACLs();
> }
>
> Note that it gets the TempDestinationWriteACLs(), even though if we are not
> a temp queue it gets the ReadACLs(). If you look in addProducer() you can
> see a similar piece of code that might be where this copy originated.
>
> I am using what looks to be the latest 4.2 SNAPSHOT (file:
> apache-activemq-4.2-20070214.034812-3.zip).
>
> lorne
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1163) bug in reading temp queue using the
tempDestinationAuthorizationEntry feature
Posted by "Jonas Lim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonas Lim resolved AMQ-1163.
----------------------------
Resolution: Fixed
resolved in trunk : r507792
> bug in reading temp queue using the tempDestinationAuthorizationEntry feature
> ------------------------------------------------------------------------------
>
> Key: AMQ-1163
> URL: https://issues.apache.org/activemq/browse/AMQ-1163
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Jonas Lim
> Assigned To: Jonas Lim
> Fix For: 4.2.0
>
>
> > Folks,
> >
> > I've been trying to use the tempDestinationAuthorizationEntry feature in 4.2
> > and I think I've found a problem. If I set up a consumer of the temp queue
> > and add it to the read permission, it always reports that I don't have
> > permission to read the queue. However, if I add that consumer to the write
> > permission on the queue it works like a charm.
> >
> > Looking at the source I think I have discovered a bulk copy/paste problem.
> > If you look at
> > org.apache.activemq.security.AuthorizationBroker.addConsumer() in the source
> > trunk, you will see this little piece of code a couple of lines from the top
> > of the method:
> >
> > if(!info.getDestination().isTemporary()) {
> > allowedACLs =
> > authorizationMap.getReadACLs(info.getDestination());
> > }else {
> > allowedACLs = authorizationMap.getTempDestinationWriteACLs();
> > }
> >
> > Note that it gets the TempDestinationWriteACLs(), even though if we are not
> > a temp queue it gets the ReadACLs(). If you look in addProducer() you can
> > see a similar piece of code that might be where this copy originated.
> >
> > I am using what looks to be the latest 4.2 SNAPSHOT (file:
> > apache-activemq-4.2-20070214.034812-3.zip).
> >
> > lorne
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.