[
https://issues.apache.org/jira/browse/HADOOP-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron T. Myers updated HADOOP-10310:
------------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
I've just committed this to trunk, branch-2, and branch-2.3.
Thanks again for the prompt reviews, gents. Much appreciated.
> SaslRpcServer should be initialized even when no secret manager present
> -----------------------------------------------------------------------
>
> Key: HADOOP-10310
> URL: https://issues.apache.org/jira/browse/HADOOP-10310
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.3.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Priority: Blocker
> Fix For: 2.3.0
>
> Attachments: HADOOP-10310.patch
>
>
> HADOOP-8783 made a change which caused the SaslRpcServer not to be
> initialized if there is no secret manager present. This works fine for most
> Hadoop daemons because they need a secret manager to do their business, but
> JournalNodes do not. The result of this is that JournalNodes are broken and
> will not handle RPCs in a Kerberos-enabled environment, since the
> SaslRpcServer will not be initialized.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
