Key pair authentication to snowflake db #1578
Replies: 1 comment 4 replies
|
Hi @petrbocek Good question, and thank you for drawing your attention to the phase out of username/password for Snowflake. One clarification though: key pair is only one of the accepted strong-auth methods. SSO/MFA via browser and OAuth are equally valid, and accounts using those aren't affected (as long as no local password is still set on the user). That matters here because TE3 already supports two of those methods for Snowflake natively:
Switching your Snowflake data source to ExternalBrowser is usually the quickest fix as it satisfies Snowflake's MFA requirement without needing key pair at all. You can set this in the connection dialog as shown above. On key pair specifically: TE3 doesn't currently expose a key-pair option in the native Snowflake connector. If you specifically need key pair (e.g. an unattended/service identity), a potential workaround is to go through an ODBC DSN instead: configure a Snowflake ODBC DSN with If native key-pair support in the Snowflake connection dialog would be valuable for you, let us know and we can track it as a feature request. Hope this unblocks you in the meantime! |

Uh oh!
There was an error while loading. Please reload this page.
Hi, Since Snowflake is phasing out username and password logins and migrating to key pair authentication, is there any way to configure this in TE3? Currently, I can't update the table schema through the defined data source in Power Query.
Thanks
Peťa
All reactions