[
https://issues.apache.org/jira/browse/QPID-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed QPID-3668.
-----------------------------
Resolution: Won't Fix
Forward development for Python is now focused on the Proton Python binding. As
a result, we are considering only defects and minor improvements for the Python
qpid.messaging API. These issues are closed "won't fix" because they are
improvements outside of that scope.
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
