[jira] [Updated] (PROTON-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1542: Labels: sasl (was: ) > 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 > Labels: sasl > Fix For: proton-c-0.21.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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1542: Fix Version/s: (was: proton-c-0.19.0) proton-c-0.21.0 > 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 > Labels: sasl > Fix For: proton-c-0.21.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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1542: Fix Version/s: (was: proton-c-0.18.0) proton-c-0.19.0 > 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.19.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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1542: Component/s: (was: cpp-binding) (was: go-binding) (was: python-binding) (was: ruby-binding) > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1542: Issue Type: Improvement (was: Bug) > 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: cpp-binding, go-binding, proton-c, python-binding, > ruby-binding >Reporter: Gordon Sim > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1542: Fix Version/s: proton-c-0.18.0 > hostname should be set on sasl-init > --- > > Key: PROTON-1542 > URL: https://issues.apache.org/jira/browse/PROTON-1542 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c, python-binding, > ruby-binding >Reporter: Gordon Sim > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
