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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/11/04 01:20:28 UTC

[jira] [Updated] (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:all-tabpanel ]

Vinod Kumar Vavilapalli updated HDFS-3745:
------------------------------------------
    Target Version/s: 2.7.3  (was: 2.7.2)

Moving out all non-critical / non-blocker issues that didn't make it out of 2.7.2 into 2.7.3.

> 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: 2.0.0-alpha
>            Reporter: Aaron T. Myers
>            Priority: Trivial
>              Labels: newbie
>         Attachments: HDFS-3745.patch
>
>
> 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)