[
https://issues.apache.org/jira/browse/HADOOP-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-9070:
--------------------------------
Attachment: HADOOP-9070.patch
Original patch was not tested correctly... There is also a problem with the
client & server knowing in all cases that SASL negotiation is complete. Due to
an earlier change in HADOOP-8999 to stop PLAIN clients from hanging waiting for
a response from the server, kerberos clients may now hang. In HADOOP-9034
there is general agreement that the server should always send a success
response, so I removed the conditional to only return success for PLAIN. I'd
like to leave HADOOP-9034 open to implement a more robust solution. Note this
patch causes RPC incompatibility, but I don't think this is a problem since 2.x
is RPC incompatible with earlier releases anyway.
> Kerberos SASL server cannot find kerberos key
> ---------------------------------------------
>
> Key: HADOOP-9070
> URL: https://issues.apache.org/jira/browse/HADOOP-9070
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ipc
> Affects Versions: 3.0.0, 2.0.3-alpha
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Blocker
> Attachments: HADOOP-9070.patch, HADOOP-9070.patch
>
>
> HADOOP-9015 inadvertently removed a {{doAs}} block around instantiation of
> the sasl server which renders a server incapable of accepting kerberized
> connections.
--
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
