You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Frank Zeng (JIRA)" <ji...@apache.org> on 2017/10/16 09:27:00 UTC

[jira] [Commented] (DIRKRB-660) Compatibility problem with hadoop when getting default credential cache

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

Frank Zeng commented on DIRKRB-660:
-----------------------------------

commit dd0d13602da3fba5eba1b7ad01a3d351a54910e1
Author: zenglinx <fr...@intel.com>
Date:   Mon Oct 16 17:25:35 2017 +0800

DIRKRB-660 Compatibility problem with hadoop when getting default credential cache


> 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
>             Fix For: 1.1.0
>
>
> 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)