[GitHub] qpid-proton pull request: PROTON-334: SASL Implementation for Prot...
Github user astitcher commented on the pull request: https://github.com/apache/qpid-proton/pull/17#issuecomment-91137151 See the wiki for more information and context: https://cwiki.apache.org/confluence/x/B5cWAw --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (PROTON-334) SASL Implementation for Proton C
[ https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486900#comment-14486900 ] ASF GitHub Bot commented on PROTON-334: --- Github user astitcher commented on the pull request: https://github.com/apache/qpid-proton/pull/17#issuecomment-91137151 See the wiki for more information and context: https://cwiki.apache.org/confluence/x/B5cWAw SASL Implementation for Proton C Key: PROTON-334 URL: https://issues.apache.org/jira/browse/PROTON-334 Project: Qpid Proton Issue Type: Wish Components: proton-c Reporter: Ted Ross Assignee: Andrew Stitcher It would be desirable to have the ability to use a plug-in module for SASL in Proton. The following implementations could then be developed: 1) A portable stand-alone plugin that does ANONYMOUS, PLAIN, and EXTERNAL 2) A Cyrus-Sasl based plugin for Linux 3) A Windows plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-334) SASL Implementation for Proton C
[ https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486890#comment-14486890 ] Andrew Stitcher commented on PROTON-334: Link to the work on github: https://github.com/astitcher/qpid-proton/commits/PROTON-334 SASL Implementation for Proton C Key: PROTON-334 URL: https://issues.apache.org/jira/browse/PROTON-334 Project: Qpid Proton Issue Type: Wish Components: proton-c Reporter: Ted Ross Assignee: Andrew Stitcher It would be desirable to have the ability to use a plug-in module for SASL in Proton. The following implementations could then be developed: 1) A portable stand-alone plugin that does ANONYMOUS, PLAIN, and EXTERNAL 2) A Cyrus-Sasl based plugin for Linux 3) A Windows plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] qpid-proton pull request: PROTON-334: SASL Implementation for Prot...
GitHub user astitcher opened a pull request: https://github.com/apache/qpid-proton/pull/17 PROTON-334: SASL Implementation for Proton-C using Cyrus SASL This work Adds some new APIs to the transport and connection objects to make a higher level abstraction for authentication. This generally makes it much easier to use authentication. It also vastly changes the Proton C API for SASL and deprecates nearly all of the previous interface that allowed reading and writing individual SASL frames. You can merge this pull request into a Git repository by running: $ git pull https://github.com/astitcher/qpid-proton PROTON-334 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/17.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #17 commit 4a09c6a17f865df10f53fa61c8d2bc88d4627bb0 Author: Andrew Stitcher astitc...@apache.org Date: 2015-04-09T06:14:14Z PROTON-334: SASL Implementation for Proton-C using Cyrus SASL This work Adds some new APIs to the transport and connection objects to make a higher level abstraction for authentication. This generally makes it much easier to use authentication. It also vastly changes the Proton C API for SASL and deprecates nearly all of the previous interface that allowed reading and writing individual SASL frames. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
