Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-3668

Python console has inconsistent interface to the authenticated user state, depending on whether saslwrapper is used or not.

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 0.13
    • Fix Version/s: None
    • Component/s: Python Client
    • Labels:
      None

      Description

      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).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                kgiusti Ken Giusti
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: