juju client cannot connect to controllers configured with an autocert-dns-name

[Martin Hilton]

If a controller is bootstrapped with a DNS name using --config autocert-dns-name then a client cannot create a secure connection to that server using that name. This seems to be because the client resolves the hostname to an IP address before requesting the https certificate and does not include the original hostname in the certificate request. The server only serves the correct signed certificate if SNI indicates it was requested for the specified hostname, the client therefore never receives a certificate with an authorized chain back to a root CA, and rightly refuses to connect.

[John A Meinel (jameinel)]

That seems like we broke something, because I'm pretty sure it used to work in this fashion. I thought that was actually how all of the JAAS controllers were originally set up.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.