The driver cannot connect to the workspace whose hostname is an internal private link hostname, this is because its domain is not added into Databricks workspace certificate. See https://github.com/databricks/databricks-sql-go/issues/223
Description
This change adds connection option WithSkipTLSHostVerify which can disable verifying the hostname in the server certificate. In this mode, TLS is susceptible to machine-in-the-middle attacks. Please only use this option when the hostname is an internal private link hostname.
Background
The driver cannot connect to the workspace whose hostname is an internal private link hostname, this is because its domain is not added into Databricks workspace certificate. See https://github.com/databricks/databricks-sql-go/issues/223
Description
This change adds connection option
WithSkipTLSHostVerify
which can disable verifying the hostname in the server certificate. In this mode, TLS is susceptible to machine-in-the-middle attacks. Please only use this option when the hostname is an internal private link hostname.Here is the usage