You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using this provider under a Linux container and we have Snowflake MFA enabled per user using the DUO push mechanism.
Unfortunately, the provider doesn't cache the MFA token, so we are pushed a new approval request each time we run. Sometimes for multiple times per deployment.
The solution to this appears like it would be quite simple. I also had a similar issue with the Snowflake Python connector and adding the following client parameters fixed it:
authenticator=username_password_mfa
client_store_temporary_credential=True
client_request_mfa_token=True
From a quick look at the design of the provider, it appears that it would be quite straight-forward to also add these parameters to the provider.
The text was updated successfully, but these errors were encountered:
(first the underlying gosnowflake connector needed capability to support connection/mfa caching. this has been added ~3 weeks back and released with 1.6.17)
We are using this provider under a Linux container and we have Snowflake MFA enabled per user using the DUO push mechanism.
Unfortunately, the provider doesn't cache the MFA token, so we are pushed a new approval request each time we run. Sometimes for multiple times per deployment.
The solution to this appears like it would be quite simple. I also had a similar issue with the Snowflake Python connector and adding the following client parameters fixed it:
From a quick look at the design of the provider, it appears that it would be quite straight-forward to also add these parameters to the provider.
The text was updated successfully, but these errors were encountered: