You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Siyao Meng (Jira)" <ji...@apache.org> on 2026/10/14 09:08:00 UTC

[jira] [Created] (HADOOP-20019) Support the IPv6 wildcard address in Kerberos _HOST substitution

Siyao Meng created HADOOP-20019:
-----------------------------------

             Summary: Support the IPv6 wildcard address in Kerberos _HOST substitution
                 Key: HADOOP-20019
                 URL: https://issues.apache.org/jira/browse/HADOOP-20019
             Project: Hadoop Common
          Issue Type: Sub-task
            Reporter: Siyao Meng
            Assignee: Siyao Meng


{{SecurityUtil.getServerPrincipal}} replaces {{_HOST}} with the local host name when the host is null, empty or {{0.0.0.0}}. The IPv6 wildcard address is not recognized, so it is copied into the principal.

A daemon that logs in with the host of its bind address therefore gets an invalid principal when it binds to the IPv6 wildcard. For example, a JournalNode with {{dfs.journalnode.rpc-address=[::]:8485}}, the IPv6 form of the default {{0.0.0.0:8485}}, logs in as {{jn/0:0:0:0:0:0:0:0@REALM}}. {{HttpServer2}} takes the SPNEGO host from its first endpoint, so an endpoint built from {{[::]:9870}} gives {{HTTP/[0:0:0:0:0:0:0:0]@REALM}}. The ResourceManager and other daemons that log in with the host of their bind address are affected the same way.

Treat the IPv6 wildcard address, in any spelling and with or without brackets, like {{0.0.0.0}}. Other hosts keep their current behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org