fix: Ensure tokens are cached when using browser authentication or basic authentication with MFA #50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The purpose of this PR is to fix the issue reported here, essentially making sure that oauth tokens are cached when using browser authentication to avoid having multiple browser windows popping in consecutive runs, even when the Snowflake account being accessed has ALLOW_ID_TOKEN option enabled.
While there, also ensured proper caching of MFA tokens (when the user account has ALLOW_CLIENT_MFA_CACHING enabled).
Implementation details:
secure-local-storage
extra tosnowflake-connector-python
dependency"client_request_mfa_token": True
and"client_store_temporary_credential": True
to the connection arguments of the SQLAlchemy engine. This is mostly relevant for Linux users, as for MacOs (at least) thesecure-local-storage
extra is enough.pre-commit
steps)