-
Notifications
You must be signed in to change notification settings - Fork 524
Environment variable to force browser-based auth #2538
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
Environment variable to force browser-based auth #2538
Conversation
The console isn't always available, and accepting both simultaneously is proving difficult.
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA (on behalf of my role at Datadog) |
|
I have read the CLA Document and I hereby sign the CLA |
The others in this file start with `SNOWFLAKE_AUTH_*`. We should do the same.
|
Thanks for the contribution! Looks good, I pushed description and linter fixes. I'm running tests in #2577 (fork branches do not have permissions for gh secrets), I'll merge the PR if everything goes well |
What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Addresses SNOW-2341451:
externalbrowsersupport for headless environments #2537 and partially SNOW-862000: Support for External Authentication while running from EMR using spark-magic #1637. It's not the optimal solution IMO (as it still requires a port-forward / network access), but is minimally invasive.Fill out the following pre-review checklist:
Please describe how your code solves the related issue.
An interactive console isn't always available, and we can't open a browser from inside docker. However, if the
SNOWFLAKE_AUTH_FORCE_SERVERis set, we'll ignore browser-open failures, and listen for the token anyways.I tested it on a Airflow docker instance running on my laptop and was able to execute queries. Used the following env vars: