[
https://issues.apache.org/jira/browse/PROTON-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378221#comment-15378221
]
ASF subversion and git services commented on PROTON-1239:
---------------------------------------------------------
Commit 0340eab4977c8a12250b0686c3f008a6da86689e in qpid-proton's branch
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=0340eab ]
PROTON-1239: Add accessor to connection for authenticated user.
- Also had to fix pn_transport_get_user() to act correctly on a server
where sasl parameters were set but sasl itself was not required.
> There is no way to query proton::connection for user
> ----------------------------------------------------
>
> Key: PROTON-1239
> URL: https://issues.apache.org/jira/browse/PROTON-1239
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
>
> There is no accessor for the user property of a connection. Either on the
> client or server side.
> There is a parallel user setter so I tend to think this is an oversight.
> It is not such an issue on the client side (as in theory you could just
> record the user you set), but on the server side the alternative is to use
> the sasl object attached to the transport, which is awkward and doesn't cover
> all the possibilities (SSL client certificates).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
