[
https://issues.apache.org/jira/browse/PROTON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243044#comment-16243044
]
Andrew Stitcher commented on PROTON-1682:
-----------------------------------------
The problem here is that the proactor will automatically bind an (effectively)
fresh new transport to the connection upon receiving the PN_CONNECTION_INIT
event. However this fresh new transport won't have any sasl object. This is
because the API has not had any opportunity to create one as it can have no
access to the trasnport object before its bound to the connection. However
unless there is a SASL object already created the remote hostname won't get
transferred from the connection to the sasl objects at bind time (because there
should not be any sasl object if it doesn't already exist).
If you set a username and possibly a password then this will force the sasl
object ot be created at bind time so this can be used as a work aaround.
> 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]
