hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9070) Kerberos SASL server cannot find kerberos key
Date Tue, 15 Jan 2013 22:30:16 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554460#comment-13554460
] 

Daryn Sharp commented on HADOOP-9070:
-------------------------------------

Yes, I believe HADOOP-8999 is where the change (or bulk of it) was made.  My memory is fuzzy,
but I think there was an existing case where a malformed protobuf exception was generated
when the client wasn't reading a final response.  The change is largely intended to support
PLAIN and/or other future SASL mechanisms, but it's definitely a bug that the client and server
cannot be sure that SASL has completed.
                
> 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
>             Fix For: 2.0.3-alpha
>
>         Attachments: HADOOP-9070.patch, 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

Mime
View raw message