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

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

Commit 1540040 from [~gsim] in branch 'qpid/trunk'
[ https://svn.apache.org/r1540040 ]

QPID-5300: correct error condition for certain unauthorized access errors

> [AMQP 1.0] Some ACL errors are returned as internal error instead of 
> unauthorized error
> ---------------------------------------------------------------------------------------
>
>                 Key: QPID-5300
>                 URL: https://issues.apache.org/jira/browse/QPID-5300
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.25
>            Reporter: JAkub Scholz
>            Assignee: Gordon Sim
>             Fix For: 0.25
>
>
> It seems when some ACL errors occur, the C++ broker is sometimes using the 
> AMQP 1.0 error code unauthorized-access and sometimes internal-error. For 
> example the "ACL denied queue access" error is amqp:unauthorized-access:
> {{[0x24ca9d0:0] <- @detach [handle=0, closed=true, error=@error 
> {condition=:"amqp:unauthorized-access", description="ACL denied queue access 
> request from ABCFR_ABCFRALMMACC1@QPID0000 
> (/home/jakub/qpid/qpid-trunk/cpp/src/qpid/broker/amqp/Authorise.cpp:72)"]]}}
> But "ACL denied queue create access" is amqp:internal-error:
> {{[0x1d14b10:0] <- @detach [handle=1, closed=true, error=@error 
> [condition=:"amqp:internal-error", description="unauthorized-access: ACL 
> denied queue create request from ABCFR_ABCFRALMMACC1@QPID0000 
> (/home/jakub/qpid/qpid-trunk/cpp/src/qpid/broker/Broker.cpp:1295)"]]}}
> I would expect that all ACL errors should be returned as 
> amqp:unauthorized-access.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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

Reply via email to