Skip to content
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

SNOW-1759607: Tri-secret secure error #1936

Closed
mikaellemoal opened this issue Oct 23, 2024 · 2 comments
Closed

SNOW-1759607: Tri-secret secure error #1936

mikaellemoal opened this issue Oct 23, 2024 · 2 comments
Labels
status-triage_done Initial triage done, will be further handled by the driver team

Comments

@mikaellemoal
Copy link

Hi,

With tri-secret-secure, Snowflake must connect to a vault, but sometime we have this error:

Caused by:*** net.snowflake.client.jdbc.SnowflakeSQLException:*** Error received from the customer managed key (CMK) provider:*** 'Internal error: Unable to authenticate with Azure KeyVault.*** Rrror message=com.microsoft.aad.msal4j.MsalClientException:*** java.net.UnknownHostException:*** login.microsoftonline.com'***

Is-it possible to modify the JDBC driver with an option to retry if this error happen ?

Regards,
Mikael

@github-actions github-actions bot changed the title Tri-secret secure error SNOW-1759607: Tri-secret secure error Oct 23, 2024
@sfc-gh-wfateem
Copy link
Collaborator

@mikaellemoal do you happen to have a full stack error that you can share?

@sfc-gh-dszmolka
Copy link
Contributor

closing this issue as it's 1 month old without answer. If you need further help, please provide the details so we could continue debugging.
Judging from the error message; there's a Snowflake-internal parameter the Support folks can set for you if this keeps repeating.

@sfc-gh-dszmolka sfc-gh-dszmolka added the status-triage_done Initial triage done, will be further handled by the driver team label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Development

No branches or pull requests

3 participants