-
Notifications
You must be signed in to change notification settings - Fork 470
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
Lighdash Preview: Snowflake MFA (Duo Push) not currently cached #3570
Comments
Is this issue still relevant? There have been no updates for 60 days, please close the issue or keep the conversation going! |
Multiple Duo Push MFA requests are also triggered in the Lightdash app - e.g. if a Dev project is being used and connecting to a Dev database in Snowflake using a user's dev user credentials that is secured by MFA. This is very non-user friendly and risks the user being locked out of Snowflake if a Duo Push is missed on the user's device. |
Here's how dbt handles it: https://docs.getdbt.com/docs/core/connect-data-platform/snowflake-setup#user--password--duo-mfa-authentication I wonder if we can add this |
According to the Snowflake docs, it looks like this isn't currently supported for the node.js SDK that we require:
I believe the only reason that we reach out to snowflake for each explore is to get the |
@owlas could we also have an option to skip that part eg: |
Curious if this can be reprioritized, once snowflakedb/snowflake-connector-nodejs#493 is complete — looks like active progress, and though they’ve missed an ETA, hopeful that it is available in the next few months (I’ve asked for an updated ETA) |
Description
When in lightdash preview, every action that sends a request to Snowflake results in a Duo Push MFA request - e.g. filter autocomplete, query run, etc. This is not user-friendly, but can be solved if MFA is cached in the jdbc string(?).
https://docs.snowflake.com/en/user-guide/security-mfa.html#using-mfa-token-caching-to-minimize-the-number-of-prompts-during-authentication-optional
What problem does this solve?
Makes Lightdash Preview more usable
The text was updated successfully, but these errors were encountered: