hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-1023) Allow http server to start as regular principal if https principal not defined.
Date Sat, 10 Jul 2010 19:47:50 GMT

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

Jakob Homan updated HDFS-1023:

        Status: Resolved  (was: Patch Available)
    Resolution: Fixed

Test failures are unrelated and this is a Kerberos change, which is currently untestable.
 I've committed this.  Resolving as fixed.

> Allow http server to start as regular principal if https principal not defined.
> -------------------------------------------------------------------------------
>                 Key: HDFS-1023
>                 URL: https://issues.apache.org/jira/browse/HDFS-1023
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>             Fix For: 0.22.0
>         Attachments: HADOOP-1023-Y20-1.patch, HDFS-1023-trunk.patch, HDFS-1023-Y20-Update-2.patch,
HDFS-1023-Y20-Update.patch, HDFS-1023-Y20.patch
> Currently limitations in Sun's KerbSSL implementation require the https server to be
run as "host/[machine]@realm." and another Sun KerbSSL limitation appears to require you to
store all principals in the same keytab, meaning fully functional, secured Namenodes require
combined keytabs.  However, it may be that one wishes to run a namenode without a secondary
namenode or other utilities that require https.  In this case, we should allow the http server
to start and log a warning that it will not be able to accept https connections.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message