Type: New Feature
Affects Version/s: 3.9.0
Fix Version/s: None
Does Hue support alternative names in TLS certs? We are using openstack and it uses the concept of private/public hostnames/IP in the cert I have both the public and private hostname are on it. But, hue can only read one and it trows an error:
"hostname we connect to "rofl.dude.rofl.com" doesn't match certificate provided commonName " lmao.rofl.com" (code THRIFTTRANSPORT):
and it keeps repeating. The openstack infrastructure forces us to use to both private and public hostname/IP since that is what Cloudera-manager/CDH can use. Somewhat similar to Amazon AWS in here:
Installing on AWS, you must use private EC2 hostnames.
When installing on an AWS instance, and adding hosts using their public names, the installation will fail when the hosts fail to heartbeat.
Use the Back button in the wizard to return to the original screen, where it prompts for a license.
Rerun the wizard, but choose "Use existing hosts" instead of searching for hosts. Now those hosts show up with their internal EC2 names.
Continue through the wizard and the installation should succeed.