Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Fri, 10 Oct 2014 19:44:34 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12747391.1412970269000.240881.1412970274918@Atlassian.JIRA>
In-Reply-To: <JIRA.12747391.1412970269000@Atlassian.JIRA>
References: <JIRA.12747391.1412970269000@Atlassian.JIRA>
 <JIRA.12747391.1412970269725@arcas>
Subject: [jira] [Created] (YARN-2677) registry punycoding of usernames
 doesn't fix all usernames to be DNS-valid
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Steve Loughran created YARN-2677:
------------------------------------

             Summary: registry punycoding of usernames doesn't fix all usernames to be DNS-valid
                 Key: YARN-2677
                 URL: https://issues.apache.org/jira/browse/YARN-2677
             Project: Hadoop YARN
          Issue Type: Sub-task
    Affects Versions: 2.6.0
            Reporter: Steve Loughran
            Assignee: Steve Loughran


The registry has a restriction "DNS-valid names only" to retain the future option of DNS exporting of the registry.

to handle complex usernames, it punycodes the username first, using Java's {{java.net.IDN}} class.

This turns out to only map high unicode-> ASCII, and does nothing for ascii-but-invalid-hostname chars, so stopping users with DNS-illegal names (e.g. with an underscore in them) from being able to register


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)