Repository navigation
Allow setting TLS settings on the underlying HTTPS agent #197
Description
Currently the settings for a custom certificate or two-way SSL are implemented on the IConnectionOptions interface but they don't surface back up to an object that the user of the library can easily manipulate; for example in ConnectionOptions. I think these options should be settable when establishing a new connection in https://github.com/databricks/databricks-sql-nodejs/blob/main/lib/DBSQLClient.ts#L120C16-L120C23
A workaround is to bypass the 'private' protections on DBSQLClient.getConnectionOptions but that is non-ideal.
Reacted by Levko Kravets and Patrick Donnelly
Activity
vuanhphung commentedon Oct 29, 2026
This was implemented in 2.1.0 (#463).
connect()now acceptscustomCaCert,clientCertandclientKeyfor mTLS, pluscheckServerCertificate, so there's no need to reach intogetConnectionOptionsanymore. See the TLS section of CONNECTION_PARAMETERS.md. I confirmed on 2.4.0 that these options reach the HTTPS agent and that connections work with them set.Closing as completed.