Eno Compton

Just to circle back here and provide some information for others who run into this issue: One thing to keep in mind is that Auto IAM AuthN has a limit...

@phoenix2x FYI it's possible to use auto IAM authn without the Go Connector. You'll need to ensure a few things: 1. The token has only sql.login scope (i.e., `https://www.googleapis.com/auth/sqlservice.login`) 2....

Native port. We're working on making this more obvious and possibly even providing some helper functions.

@joehan This issue might be lacking some details. We recently added support for specifying a GoogleAuth value in #238 with an example usage [in the README](https://github.com/GoogleCloudPlatform/cloud-sql-nodejs-connector?tab=readme-ov-file#using-with-google-auth-library-nodejs-client-credentials). I assume GoogleAuth doesn't...

Have you tried something like this? I haven't tested this, and am just following the types, so this might be wrong. ``` node.js import {JWT} from 'google-auth-library'; import {Connector} from...

Thanks, @joehan. This is on our list, but below a number of high priority items.

@edosrecki Have you tried with the following? ``` javascript const clientOpts = await connector.getTediousOptions({ instanceConnectionName: 'my-project.my-region.my-instance', ipType: IpAddressTypes.PUBLIC, authType: AuthTypes.PASSWORD, // adding these two options encrypt: true, trustServerCertificate: true })...

This is related to how SQL Server doesn't have support for Unix sockets -- which is how Postgres and MySQL avoid the problem. They accept unencrypted connections through a Unix...

We need to hold off on this until PSC DNS is populated in all existing certificates.

Via @jackwotherspoon > "HostName" contains the fully qualified DNS hostname of the server, as understood by the client. The hostname is represented as a byte string using ASCII encoding without...