[
https://issues.apache.org/jira/browse/AVRO-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905212#action_12905212
]
Doug Cutting commented on AVRO-641:
-----------------------------------
> Doesn't always using SASL result in an extra roundtrip at connection startup?
No, it's piggybacked. From the RFC:
The mechanism consists of a single message from the client to the server.
Before the first request the client sends the SASL anonymous message, but it
does not block waiting for a response, instead it directly proceeds to write
the request. The anonymous message has no response and SASL is complete once
that message has been sent. If the server does not accept the anonymous
mechanism, it closes the connection and logs an error. When a client uses the
anonymous mechanism we should probably catch EOFException and suggest that
there may have been an authentication problem.
> add SASL to socket transport
> ----------------------------
>
> Key: AVRO-641
> URL: https://issues.apache.org/jira/browse/AVRO-641
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 1.4.1
>
> Attachments: AVRO-641.patch, AVRO-641.patch, AVRO-641.patch
>
>
> Java's socket transport is non-standard (not in the Avro spec) but might
> serve as a prototype of a future standard transport (AVRO-341).
> It would be useful to extend it to support SASL-based authentication and
> encryption.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
