[
https://issues.apache.org/jira/browse/PROTON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243053#comment-16243053
]
Andrew Stitcher commented on PROTON-1682:
-----------------------------------------
There are various possible fixes.
they essentially all require access to the transport object before it gets
bound to the connection object though. How this is achieved is subject to
debate, possibilities:
* Instead of having the proactor code create a new transport object when you
create an outgoing connection, you pass the transport object in, so you have
access to the object then or can keep track of it for later.
* At the point of the PN_CONNECTION_INIT event if you could get access the the
transport the proactor is about to bind to the connection then you could force
the sasl object creation then. Perhaps modify the pn_event_transport() API to
support this by checking for a transport attached to the event. THis would need
to be put there by the proactor code.
Other possibilities don't require access to a transport but would changing
pn_connection_t to keep track of some more state that would force sasl creation.
Or changing the proactor to keep track of whether sasl is required somehow and
to ensure that it happens when binds the connection.
[~aconway] any other thoughts?
> SASL auth with GSSAPI fails: hostname is not set
> ------------------------------------------------
>
> Key: PROTON-1682
> URL: https://issues.apache.org/jira/browse/PROTON-1682
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, proton-c
> Affects Versions: proton-c-0.18.0
> Reporter: Andrew Stitcher
> Assignee: Cliff Jansen
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
