[
https://issues.apache.org/jira/browse/PROTON-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tim taylor updated PROTON-1606:
-------------------------------
Description:
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.
was:
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 (SERVER).
...
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();
....
> (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: [email protected]
For additional commands, e-mail: [email protected]
