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-980268: JWT Expiry and Query Execution Time in Snowflake JDBC Driver #1572

Closed
katamotokosuke opened this issue Nov 29, 2023 · 0 comments
Labels

Comments

@katamotokosuke
Copy link

Hello,

it's probably not bug, I would like to confirm driver specification.
I have a question regarding the behavior of a driver when passing a user and private key. I understand from the documentation that the driver automatically adopts snowflake_jwt as the authenticator in this scenario.

While reading the driver's source code, I noticed that the JWT expiry is set to one minute:

// expiration is 60 seconds later
Date exp = new Date(iat.getTime() + 60L * 1000);

However, when using the driver to execute a query like select system$wait(6000); in Snowflake, it seems to wait appropriately.

My questions are as follows:

  1. Is this behavior intentional?
  2. If the behavior in question 1 is intentional, what does this 'exp' represent?
  3. What is the appropriate way to control the maximum time the driver waits for a query execution when connected to Snowflake?

Thank you in advance for your assistance.

@github-actions github-actions bot changed the title JWT Expiry and Query Execution Time in Snowflake JDBC Driver SNOW-980268: JWT Expiry and Query Execution Time in Snowflake JDBC Driver Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant