[
https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200281#comment-16200281
]
Andrew Stitcher edited comment on PROTON-1542 at 10/11/17 1:38 PM:
-------------------------------------------------------------------
[~gsim] Can you explain how this is related to PROTON-1535. I may have
understood once, but it escapes me now. That JIRA seems to be about the server
end of the connection setting its idea of the _local_ hostname. However this
JIRA seems to be about the client end setting the connected to hostname.
Is this correct?
[editted for typos]
was (Author: astitcher):
[~gsim] Can you explain how this is related to PROTON-1535. I may have
understood once, but it escapes me now. That JIRA seems to be about the serfer
end of the connection setting its idea of the _local_ hostname. However this
JIRA seems to be about the client end setting the connected to hostname.
Is This correct?
> hostname should be set on sasl-init
> -----------------------------------
>
> Key: PROTON-1542
> URL: https://issues.apache.org/jira/browse/PROTON-1542
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Reporter: Gordon Sim
> Assignee: Andrew Stitcher
> Fix For: proton-c-0.18.0
>
>
> For a multi-tenant service/server, where each tenant has its own user base,
> the hostname in the sasl-init frame provides a convenient way of determining
> the correct tenant to authenticate for.
> At present this is not set for any proton-c based client. It is similar to
> the SNI information included in the TLS layer initiation (if such a layer is
> in use).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
