[jira] [Commented] (PROTON-1255) connection_engine support for built-in proton SSL/SASL
[ https://issues.apache.org/jira/browse/PROTON-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627466#comment-15627466 ] ASF subversion and git services commented on PROTON-1255: - Commit 507c9356692858a81916a4a8802fbc6b2302bc5f in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=507c935 ] PROTON-1255: Remove pn_connection_engine_start Bind the connection automatically in pn_connection_engine_dispatch after the user has processed the PN_CONNECTION_INIT event. This removes the need to manually call start and allows user handlers to set security settings in their handler on PN_CONNECTION_INIT, before the bind. > connection_engine support for built-in proton SSL/SASL > -- > > Key: PROTON-1255 > URL: https://issues.apache.org/jira/browse/PROTON-1255 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Critical > Fix For: 0.15.0 > > > Make sure proton's built-in SSL and SASL work fully with the connection > engine for all bindings that have one (C, C++, Go) > The connection_engine also allows a secure connection to be established > externally. Check that we have sufficient hooks to pass external security > principal info to the handler via connection and transport properties. -- 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
[jira] [Commented] (PROTON-1255) connection_engine support for built-in proton SSL/SASL
[ https://issues.apache.org/jira/browse/PROTON-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15606338#comment-15606338 ] ASF subversion and git services commented on PROTON-1255: - Commit 507c9356692858a81916a4a8802fbc6b2302bc5f in qpid-proton's branch refs/heads/aconway-libuv-driver from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=507c935 ] PROTON-1255: Remove pn_connection_engine_start Bind the connection automatically in pn_connection_engine_dispatch after the user has processed the PN_CONNECTION_INIT event. This removes the need to manually call start and allows user handlers to set security settings in their handler on PN_CONNECTION_INIT, before the bind. > connection_engine support for built-in proton SSL/SASL > -- > > Key: PROTON-1255 > URL: https://issues.apache.org/jira/browse/PROTON-1255 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Critical > Fix For: 0.15.0 > > > Make sure proton's built-in SSL and SASL work fully with the connection > engine for all bindings that have one (C, C++, Go) > The connection_engine also allows a secure connection to be established > externally. Check that we have sufficient hooks to pass external security > principal info to the handler via connection and transport properties. -- 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
[jira] [Commented] (PROTON-1255) connection_engine support for built-in proton SSL/SASL
[ https://issues.apache.org/jira/browse/PROTON-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605510#comment-15605510 ] ASF subversion and git services commented on PROTON-1255: - Commit 507c9356692858a81916a4a8802fbc6b2302bc5f in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=507c935 ] PROTON-1255: Remove pn_connection_engine_start Bind the connection automatically in pn_connection_engine_dispatch after the user has processed the PN_CONNECTION_INIT event. This removes the need to manually call start and allows user handlers to set security settings in their handler on PN_CONNECTION_INIT, before the bind. > connection_engine support for built-in proton SSL/SASL > -- > > Key: PROTON-1255 > URL: https://issues.apache.org/jira/browse/PROTON-1255 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Critical > Fix For: 0.15.0 > > > Make sure proton's built-in SSL and SASL work fully with the connection > engine for all bindings that have one (C, C++, Go) > The connection_engine also allows a secure connection to be established > externally. Check that we have sufficient hooks to pass external security > principal info to the handler via connection and transport properties. -- 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
[jira] [Commented] (PROTON-1255) connection_engine support for built-in proton SSL/SASL
[ https://issues.apache.org/jira/browse/PROTON-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507899#comment-15507899 ] ASF subversion and git services commented on PROTON-1255: - Commit 3d9fe620758bd55afae6af76b50a2bd5d6839232 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=3d9fe62 ] PROTON-1255: connection_engine separate bind from _init SASL/SSL properties must be set on connection and transport *before* the pn_transport_bind() call, move it out of pn_connection_engine_init() and add pn_connection_engine_start() that must be called before using the engine but after security (and other) properties are set. Updated the Go and C++ engines accordingly. > connection_engine support for built-in proton SSL/SASL > -- > > Key: PROTON-1255 > URL: https://issues.apache.org/jira/browse/PROTON-1255 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Critical > Fix For: 0.15.0 > > > Make sure proton's built-in SSL and SASL work fully with the connection > engine for all bindings that have one (C, C++, Go) > The connection_engine also allows a secure connection to be established > externally. Check that we have sufficient hooks to pass external security > principal info to the handler via connection and transport properties. -- 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
[jira] [Commented] (PROTON-1255) connection_engine support for built-in proton SSL/SASL
[ https://issues.apache.org/jira/browse/PROTON-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385789#comment-15385789 ] Alan Conway commented on PROTON-1255: - Important note: for external SSL the user will need to set the host and username on the connection object, that should be made clear in docs/examples. For proton-internal SSL, make sure the engine picks up host/user from the internal SSL objects. > connection_engine support for built-in proton SSL/SASL > -- > > Key: PROTON-1255 > URL: https://issues.apache.org/jira/browse/PROTON-1255 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Critical > Fix For: 0.15.0 > > > Make sure proton's built-in SSL and SASL work fully with the connection > engine for all bindings that have one (C, C++, Go) > The connection_engine also allows a secure connection to be established > externally. Check that we have sufficient hooks to pass external security > principal info to the handler via connection and transport properties. -- 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
[jira] [Commented] (PROTON-1255) connection_engine support for built-in proton SSL/SASL
[ https://issues.apache.org/jira/browse/PROTON-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379616#comment-15379616 ] Alan Conway commented on PROTON-1255: - Add the following examples and fix any issues (hopefully none) that arise: 1. connection_engine example showing how to use protons built-in SSL, adapted from existing SSL example. 2. Go example using native Go SSL with the proton engine. Both examples should print the authenticated SSL user from a proton on-open handler. > connection_engine support for built-in proton SSL/SASL > -- > > Key: PROTON-1255 > URL: https://issues.apache.org/jira/browse/PROTON-1255 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Critical > > Make sure proton's built-in SSL and SASL work fully with the connection > engine for all bindings that have one (C, C++, Go) > The connection_engine also allows a secure connection to be established > externally. Check that we have sufficient hooks to pass external security > principal info to the handler via connection and transport properties. -- 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