You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2017/10/06 12:10:00 UTC
[jira] [Updated] (PROTON-1606) add option to disable the SASL layer
when using the Reactor
[ https://issues.apache.org/jira/browse/PROTON-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated PROTON-1606:
-----------------------------------
Summary: add option to disable the SASL layer when using the Reactor (was: (Proton-J) Using Sasl needs to be optional for Client Role)
> add option to disable the SASL layer when using the Reactor
> -----------------------------------------------------------
>
> 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