You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2015/03/16 17:11:38 UTC
[jira] [Commented] (HDFS-3745) fsck prints that it's using KSSL
even when it's in fact using SPNEGO for authentication
[ https://issues.apache.org/jira/browse/HDFS-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363409#comment-14363409 ]
Harsh J commented on HDFS-3745:
-------------------------------
I think it should not be harmful to keep the sub-mechanism info around. We could just rename the KERBEROS_SSL into KERBEROS_SPNEGO on trunk I think, since we do not use/support KERBEROS_SSL (KSSL) anymore in trunk and branch-2?
> fsck prints that it's using KSSL even when it's in fact using SPNEGO for authentication
> ---------------------------------------------------------------------------------------
>
> Key: HDFS-3745
> URL: https://issues.apache.org/jira/browse/HDFS-3745
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client, security
> Affects Versions: 1.2.0, 2.0.0-alpha
> Reporter: Aaron T. Myers
> Priority: Trivial
> Labels: newbie
>
> In branch-2 (which exclusively uses SPNEGO for HTTP authentication) and in branch-1 (which can optionally use SPNEGO for HTTP authentication), running fsck will print the following, which isn't quite right:
> {quote}
> FSCK started by hdfs (auth:KERBEROS_SSL) from...
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)