Python console has inconsistent interface to the authenticated user state,
depending on whether saslwrapper is used or not.
---------------------------------------------------------------------------------------------------------------------------
Key: QPID-3668
URL: https://issues.apache.org/jira/browse/QPID-3668
Project: Qpid
Issue Type: Improvement
Components: Python Client
Affects Versions: 0.13
Reporter: Ken Giusti
If the python client uses the sasl service to provide authentication, then the
authenticated user-id is provided via the connection object. However, if sasl
is not available, the python client will use its integrated PLAIN or ANONYMOUS
mechanism. In this case, no information appears to be available to determine
the actual user-id used (or anonymous). For example:
self.conn = Connection(connSock, username=self.authUser,
password=self.authPass,
mechanism = self.mechanisms, host=self.host,
service="qpidd")
uid = self.conn.user_id
'uid' above is None if internal PLAIN or ANONYMOUS was used. It is set if sasl
was used (and -could- be 'anonymous' etc).
It would be consistent if the uid was set in either case (sasl or non-sasl).
--
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]
