Eno Compton

> when this happens I can see that the server asks the client for the password and its sent. That's interesting. The way Auto IAM AuthN works is that the...

Nice find. I suspect this is due to https://github.com/GoogleCloudPlatform/cloud-sql-go-connector/issues/771. I'll get this fixed. Thanks for your careful debugging.

This also manifests as https://github.com/GoogleCloudPlatform/cloud-sql-proxy/issues/2224. This is definitely caused by https://github.com/GoogleCloudPlatform/cloud-sql-go-connector/issues/771. I'll have a fix ready to try today or tomorrow.

PR to fix this in cloudsqlconn is here: https://github.com/GoogleCloudPlatform/cloud-sql-go-connector/pull/806. We'll get that out in a release soon.

The latest release of the Go Connector has a fix: https://github.com/GoogleCloudPlatform/cloud-sql-go-connector/releases/tag/v1.10.1.

@frko Would you mind opening a new issue? This sounds like something different.

A couple of questions: - How long do your background jobs typically run for? - Why are your jobs connecting to the database during shutdown? As for suggestions: - The...

> If it just so happens that the token is expired (and a refresh is necessary), why would this fail? The Go Connector uses a refresh ahead cache internally that...

For debug logging, use [`cloudsqlconn.WithContextLogger`](https://github.com/GoogleCloudPlatform/cloud-sql-go-connector/blob/1bc270ef83731564ddaa056005ead5031274e303/options.go#L260).

Your setup looks perfectly correct. > so it's definitely intermittent but I'm a bit surprised. Same here. It can happen that the backend call to verify the IAM principal fails,...