[YARN-2677] registry punycoding of usernames doesn't fix all usernames to be DNS-valid

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.6.0
• Component/s: api, resourcemanager
• Target Version/s: 2.6.0
• Hadoop Flags: Reviewed
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 10/Oct/14 19:44
• Updated: 01/Dec/14 03:08
• Resolved: 30/Oct/14 22:33

Description

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

Issue Links

• breaks: SLIDER-500 registration failing if username isn't valid DNS entry
• is depended upon by: SLIDER-582 Registry test may fail if ~ expands to a path with upper case
• is depended upon by: SLIDER-149 Support a YARN service registry