[
https://issues.apache.org/jira/browse/PROTON-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-665:
----------------------------------
Assignee: Rafael H. Schloming (was: Ted Ross)
Fix Version/s: 0.10
Rafi appears to have wired this up in 0.10 via commit
940d843f36cb4cceb7f2a6bde8c5b78247392384
https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=940d843f36cb4cceb7f2a6bde8c5b78247392384
That coincided with the new SASL API and behaviours in proton-c for 0.10, such
that a Transport with SASL handling enabled will by default still allow AMQP
connections that skip establishing a SASL layer first. This behaviour can be
disabled using the Sasl#allowSkip method for transports that don't want to
allow connections without a SASL layer.
> SASL Servers need to be able to optionally handle clients that don't use SASL
> -----------------------------------------------------------------------------
>
> Key: PROTON-665
> URL: https://issues.apache.org/jira/browse/PROTON-665
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
> Affects Versions: 0.7
> Reporter: Robbie Gemmell
> Assignee: Rafael H. Schloming
> Fix For: 0.10
>
>
> A proton-based server that uses SASL for authentication needs to be able to
> optionally accept connections from clients that do not use SASL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
