[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639994#comment-13639994
]
Luke Lu commented on HADOOP-9421:
---------------------------------
bq. I was trying to point out I don't think the client can make an intelligent
discussion about a mechanism.
Don't you think that most clients just use one secure mechanism in most common
use cases (for containers/tasks, it's digest/dt, for app/job submission, it's
either gssapi/krb5 _or_ digest/ldap etc depending on site config), while
servers support multitude of mechanisms?
Client can also cache previous server response and select the most appropriate
mechanisms for subsequent connections.
> Add full length to SASL response to allow non-blocking readers
> --------------------------------------------------------------
>
> Key: HADOOP-9421
> URL: https://issues.apache.org/jira/browse/HADOOP-9421
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 2.0.3-alpha
> Reporter: Sanjay Radia
> Assignee: Junping Du
> Attachments: HADOOP-9421.patch
>
>
--
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
