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

Ken Giusti resolved QPID-3667.
------------------------------

    Resolution: Fixed
    
> Python QMF console can provide the incorrect user-id under some circumstances.
> ------------------------------------------------------------------------------
>
>                 Key: QPID-3667
>                 URL: https://issues.apache.org/jira/browse/QPID-3667
>             Project: Qpid
>          Issue Type: Bug
>          Components: Qpid Managment Framework
>    Affects Versions: 0.14
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>            Priority: Minor
>             Fix For: 0.15
>
>
> If "saslwrapper" is not available, the python console will support ANONYMOUS 
> and PLAIN auth mechanisms. PLAIN requires a username/password be specified in 
> the broker's URL.  If the broker only supports ANONYMOUS, the QMF python 
> console will incorrectly set the user-id field of each message to the value 
> that was specified in the URL as if PLAIN was used, even though it probably 
> will not match the ANONYMOUS user.
> This will result in the following exception: 
> qpid-stat -c joe/[email protected]:5672
> Failed: SessionException - ExecutionException(error_code=403,
> command_id=serial(29), class_code=0, command_code=0, field_index=0,
> description=u'unauthorized-access: authorised user id : anonymous@QPID but 
> user
> id in message declared as joe (qpid/broker/SemanticState.cpp:473)',
> error_info={}, channel=1, id=serial(2))

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to