hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Omkar Vinit Joshi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9789) Support server advertised kerberos principals
Date Mon, 12 Aug 2013 22:31:48 GMT

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

Omkar Vinit Joshi commented on HADOOP-9789:
-------------------------------------------

Hi Daryn,

I found a difference between older and newer code in terms of serverId. Is it expected this
way?

* Location :- org.apache.hadoop.security.SaslRpcServer.java
** Kerberos principal name is hdfs/localhost@LOCALHOST
** older :-
*** protocol :- hdfs
*** serverId :- *localhost*
** newer :-
*** protocol :- hdfs
*** serverId :- *localhost@LOCALHOST* (why it is instance@realm now?)
can you please give me more information and let me know if I am missing anything.
I am using below hadoop.security.auth_to_local config in core-site.xml
hadoop.security.auth_to_local : "RULE:[1:$1@$0](.*@LOCALHOST)s/@.*//DEFAULT"
                
> Support server advertised kerberos principals
> ---------------------------------------------
>
>                 Key: HADOOP-9789
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9789
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: ipc, security
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Critical
>             Fix For: 3.0.0, 2.1.1-beta
>
>         Attachments: HADOOP-9789.patch, HADOOP-9789.patch, hadoop-ojoshi-datanode-HW10351.local.log,
hadoop-ojoshi-namenode-HW10351.local.log
>
>
> The RPC client currently constructs the kerberos principal based on the a config value,
usually with an _HOST substitution.  This means the service principal must match the hostname
the client is using to connect.  This causes problems:
> * Prevents using HA with IP failover when the servers have distinct principals from the
failover hostname
> * Prevents clients from being able to access a service bound to multiple interfaces.
 Only the interface that matches the server's principal may be used.
> The client should be able to use the SASL advertised principal (HADOOP-9698), with appropriate
safeguards, to acquire the correct service ticket.

--
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