[
https://issues.apache.org/jira/browse/HADOOP-20019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HADOOP-20019:
--------------------------------
Fix Version/s: 3.5.1
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.4, 3.5.1, 3.6.0
>
>
> {{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
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
