[
https://issues.apache.org/jira/browse/PROTON-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308528#comment-16308528
]
Tim Taylor commented on PROTON-1718:
------------------------------------
I know that the service is functioning correctly in this scenario. When I
provide a custom Sasl implementation to be used instead of the usual SaslImpl
implementation, and I use the same init/challenge response data as above, the
flow works as intended. It seems like the timing for when you call
sasl.send(...) really matters because when I send the challenge response data
within the sasl.handleChallenge(...) event method, the response frame is
written immediately and I receive the next challenge correctly. When I try to
send the challenge response from a separate thread upon sasl.pending() being
non-zero, I get no response.
What am I doing wrong here?
> (Proton-J) Custom Sasl
> ----------------------
>
> Key: PROTON-1718
> URL: https://issues.apache.org/jira/browse/PROTON-1718
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
> Affects Versions: proton-j-0.24.0
> Reporter: Tim Taylor
> Labels: features
>
> I would like to be able to provide a custom SASL implementation for Proton-j
> to use instead of being forced to use the default SaslImpl.java
> implementation.
> Ideally, code like below would be possible
> private class CustomSasl implements org.apache.qpid.proton.engine.Sasl
> {
> ...
> }
> ...
> ...
> //transport.sasl(...) saves the provided sasl implementation and uses it
> internally
> Sasl sasl = transport.sasl(new CustomSasl());
> Do you currently have a workaround that would allow me to use Proton-J this
> way?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
