[
https://issues.apache.org/jira/browse/QPID-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated QPID-2112:
---------------------------
Attachment: QPID-2112.patch
This patch implements the proposal. Note that a hook has been provided for
Windows (but not tested).
> C++ Client: Facility needed for app to extract the user-ID in use for a
> connection
> -----------------------------------------------------------------------------------
>
> Key: QPID-2112
> URL: https://issues.apache.org/jira/browse/QPID-2112
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Client
> Affects Versions: 0.5
> Reporter: Ted Ross
> Priority: Minor
> Fix For: 0.6
>
> Attachments: QPID-2112.patch
>
>
> When using GSSAPI as the authentication mechanism, the client application
> does not know the identity used for an AMQP connection. This is because the
> SASL library automatically gets the identity from a keytab file and uses it
> to authenticate with the broker.
> If the application wishes to place the userID into the message properties for
> a produced message, it needs to be able to get the information from
> somewhere. I propose that the information be copied into the "negotiated
> settings" for a connection at the completion of the authentication exchange.
> Then, the client can get the identity string be calling
> "getNegotiatedSettings" on the connection. This change does not affect the
> API or ABI of the interface. It only enhances the meaning of the "username"
> field in negotiated settings.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
