You are viewing a plain text version of this content. The canonical link for it is here.

Posted to proton@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2012/11/05 20:52:14 UTC

[jira] [Assigned] (PROTON-119) Engine can switch from SASL to plain AMQP transport too soon

     [ https://issues.apache.org/jira/browse/PROTON-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gordon Sim reassigned PROTON-119:
---------------------------------

    Assignee: Gordon Sim
    
> 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
>            Assignee: 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