[
https://issues.apache.org/jira/browse/PROTON-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-119:
------------------------------
Attachment: sasl_engine.patch
One possible fix... this simply adds a flag to track whether the init has been
sent and uses that in deciding when to switch output.
> Engine can switch from SASL to plain AMQP transport too soon
> ------------------------------------------------------------
>
> Key: PROTON-119
> URL: https://issues.apache.org/jira/browse/PROTON-119
> Project: Qpid Proton
> Issue Type: New Feature
> Components: proton-j
> Affects Versions: 0.1, 0.2
> Reporter: Gordon Sim
> Fix For: 0.3
>
> Attachments: sasl_engine.patch
>
>
> The engine gets output from the AMQP engine rather than SASL wrapper as soon
> as the SASl negotiation is marked as done. In the case where the 'server'
> only supports ANONYMOUS and immediately sends an outcome without actually
> waiting for the initial frame from the client, this happens too soon, before
> the init is sent (and even the SASL header).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
