[ 
https://issues.apache.org/jira/browse/DIRKRB-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank Zeng updated DIRKRB-660:
------------------------------
    Description: 
Hadoop gets credential cache file from "/tmp/krb5cc_[uid]" when enable 
kerberos, but kerby save credential cache file in 
"/tmp/krb5_[principalName].cc" by default.
When using kerby KDC as hadoop kerberos KDC, the rpc authentication can't be 
failed. I think kerby should save credential cache file like the MIT kerberos. 

  was:
Hadoop gets credential cache file from "/tmp/krb5cc_{uid}" when enable 
kerberos, but kerby save credential cache file in 
"/tmp/krb5_{principalName}.cc" by default.
When using kerby KDC as hadoop kerberos KDC, the rpc authentication can't be 
failed. I think kerby should save credential cache file like the MIT kerberos. 


> Compatibility problem with hadoop when getting default credential cache
> -----------------------------------------------------------------------
>
>                 Key: DIRKRB-660
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-660
>             Project: Directory Kerberos
>          Issue Type: Bug
>            Reporter: Frank Zeng
>            Assignee: Frank Zeng
>
> Hadoop gets credential cache file from "/tmp/krb5cc_[uid]" when enable 
> kerberos, but kerby save credential cache file in 
> "/tmp/krb5_[principalName].cc" by default.
> When using kerby KDC as hadoop kerberos KDC, the rpc authentication can't be 
> failed. I think kerby should save credential cache file like the MIT 
> kerberos. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to