qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-1606) (Proton-J) Using Sasl needs to be optional for Client Role
Date Fri, 06 Oct 2017 12:08:00 GMT

    [ https://issues.apache.org/jira/browse/PROTON-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194506#comment-16194506
] 

ASF subversion and git services commented on PROTON-1606:
---------------------------------------------------------

Commit 819e4c3a468f5b0cd65625f86edca82f448468aa in qpid-proton-j's branch refs/heads/master
from [~timtay]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=819e4c3 ]

PROTON-1606: Added ability to make SASL communication optional for CLIENT role

Previously, the IOhandler created to be the global handler automatically created the SASL
layer whether a user of the library wanted it or not. This commit exposes an option when creating
the reactor to disable creating the SASL layer at all.

https://issues.apache.org/jira/browse/PROTON-1606


> (Proton-J) Using Sasl needs to be optional for Client Role
> ----------------------------------------------------------
>
>                 Key: PROTON-1606
>                 URL: https://issues.apache.org/jira/browse/PROTON-1606
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-j
>    Affects Versions: proton-j-0.22.0
>         Environment: N/A
>            Reporter: Tim Taylor
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> In order for my application to use Proton-j for amqps messaging, the Sasl layer cannot
be created by the global handler (IOHandler) at CONNECTION_LOCAL_OPEN time. The code below
breaks our ability to use proton-j for amqps messaging as a CLIENT against our service.
> ...
> sasl = transport.sasl();
> sasl.client();
> sasl.setMechanisms("ANONYMOUS");
> ...
> I need these three lines of code to be optional in the global handler, or for a new API
that allows a transport implementation to undo creating the Sasl layer.
> Something like:
>     ....
>     Transport transport = event.getConnection().getTransport();
>     transport.disableSasl();
>     ....
> The service I am hitting against is not using Proton-j as the SERVER role.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message