-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DUO MFA authentication doesn't work with Snowflake version 8.24+ #1131
Comments
Thank you for opening this - we will look into it and discuss it with Snowflake to confirm the change here. |
@nikzavada I'm curious when you might have seen this behavior change? Did you have MFA enabled already and working with dbt? It appears this has been implemented a while ago at Snowflake so trying to better understand what the change might have been. |
@amychen1776 we just enabled the MFA and I was trying to set it up in dbt to not to approve every run but it didn't work and I spent some time looking around and eventually I came here with my assumption about it :) |
@nikzavada That's helpful to note! I wonder if it could be related to this issue where it's not caching the connection. Would you be able to provide a cleaned up version of your profiles.yml (with no sensitive information)? |
@amychen1776 not sure if that can be related. This is a shortened profiles.yml that currently in use
|
@nikzavada could you try to set the reuse_connections to True in your profile? Just to also be clear, every new dbt command you run is now requiring an Duo approval? Would you be able to share the logs? In speaking to Snowflake about this, they also asked if you could open up a support ticket so they can help debug. I have turned on MFA for my account but can't seem to reproduce this error. |
@nikzavada I think we figured it out. Have you ran |
@amychen1776 I tried to use reuse_connection set to True and I ran And I still need to approve every dbt command I run. May I ask you what is your Snowflake version? |
@nikzavada I'm on 8.27.1. I think we might have exhausted working via github. Would you be open to reaching out to me via email ([email protected]) or dbt slack? |
I'm going to close this issue for now since we have not been able to recreate it and we do believe this might be a configuration error. Please reach out to me to help debug. |
@amychen1776 I just discovered that it doesn't work for me only when I use dbt installed with Docker (docker pull ghcr.io/dbt-labs/dbt-snowflake:1.7.1). I just installed dbt with pip and everything works as expected |
@nikzavada that's so helpful to know! Thank you |
Is this a new bug in dbt-snowflake?
Current Behavior
In the current version of dbt-snowflake the next additional parameter has been used to support caching of the token
result["client_request_mfa_token"] = True
Expected Behavior
I believe based on this documentation https://docs.snowflake.com/en/user-guide/security-mfa#label-mfa-token-caching
the new parameter
result["authenticator"] = "username_password_mfa"
is required to support the expected caching behavior.
Steps To Reproduce
Every dbt build command requires a DUO approval with Snowflake 8.26
Relevant log output
No response
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: