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

robinlin commented on RANGER-399:
---------------------------------

The problem is still there, and the config is
{noformat}
{
    "username": "[email protected]",
    "password": "hadoop",
    "fs.default.name": "hdfs://allinone:8020",
    "hadoop.security.authorization": "false",
    "hadoop.security.authentication": "kerberos",
    "hadoop.security.auth_to_local": "RULE:[2:$1@$0]([rn]m@.*)s/.*/yarn/        
RULE:[2:$1@$0](jhs@.*)s/.*/mapred/        RULE:[2:$1@$0]([nd]n@.*)s/.*/hdfs/    
    RULE:[2:$1@$0](hm@.*)s/.*/hbase/        RULE:[2:$1@$0](rs@.*)s/.*/hbase/    
    DEFAULT",
    "dfs.datanode.kerberos.principal": "dn/[email protected]",
    "dfs.namenode.kerberos.principal": "nn/[email protected]",
    "dfs.secondary.namenode.kerberos.principal": "nn/[email protected]",
    "hadoop.rpc.protection": "-",
    "commonNameForCertificate": "-"
}
{noformat}

The result of "listprincs"
{noformat}
kadmin.local:
kadmin.local:  listprincs
HTTP/[email protected]
K/[email protected]
[email protected]
[email protected]
dn/[email protected]
falcon/[email protected]
[email protected] <---- Here is the corresponding principle
hbase/[email protected]
[email protected]
[email protected]
hive/[email protected]
{noformat}

> Testing connection at a Kerberized cluster
> ------------------------------------------
>
>                 Key: RANGER-399
>                 URL: https://issues.apache.org/jira/browse/RANGER-399
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 0.4.1
>         Environment: any
>            Reporter: robinlin
>            Assignee: Ramesh Mani
>
> Hi all
> The connection testing seems malfunctioned in a Kerberized Cluster.
> Such as HDFS repository, when I traced the source code, I found it needs the 
> path of keytab, but there is no place to specify the path on the web ui. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to