I’ve been trying to connect snowflake connctor to looker studio.
Our orgnization changed to SSO in Snowflake and we no longer have a password to login.
I have a dedicated service user account to connect Snowflake to Looker Studio and here, I had to use RSA Key Pair.
While using Community Connector, I can only see username/password pattern but no the Key-Pair Authentication. So, all this time, I have been using my unencrypted private key as the password (without headers and footers).
It works good sometimes and suddenly the connection falls out giving me “Couldn’t obtain the token“ or “JWT_TOKEN_INAVLID_EXPIRATION_TIME“ errors.
Looker Studio’s native Snowflake connector currently supports username/password authentication and does not have built‑in RSA key pair support for SSO or key‑based service accounts. Using the private key in the password field is an unsupported workaround, which can lead to token expiration or intermittent failures like the JWT_TOKEN_INVALID_EXPIRATION_TIME you’re seeing. For a more stable setup, you’ll need to either provision a Snowflake user with a password specifically for Looker Studio or build a custom Community Connector in Apps Script that implements Snowflake’s key‑pair auth flow and token refresh logic.
Currently I’m extracting all my data sources and connecting back in. I hope that stays in place.
I don’t think our org has an option of creating a password but building a custom Connector sounds like a plan. Would you mind pointing me towards the resource? Thank you for the help!