You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2016/07/15 16:09:20 UTC
[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&focusedCommentId=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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org