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

[Bug]: Snowflake OCSP based Certificated Revocation Logs #2527

Closed
mcrascal opened this issue Sep 12, 2024 · 1 comment · Fixed by #2631
Closed

[Bug]: Snowflake OCSP based Certificated Revocation Logs #2527

mcrascal opened this issue Sep 12, 2024 · 1 comment · Fixed by #2631
Labels
bug Something isn't working connectors Database connectors to-review Evidence team to review

Comments

@mcrascal
Copy link
Member

Describe the bug

Snowflake connector prints an unpleasant warning on each tick of a run-sources into the console.

fail open is the default behaviour for their node driver. Ideally our connector could avoid triggering this warning, but at the very least we should catch it and present it in a way that doesn't disrupt the console feedback on a sources run.

◣ Processing...{"level":"WARN","message":"[2:11:03.504 PM]: WARNING!!! using fail-open to connect. Driver is connecting to an HTTPS endpoint without OCSP based Certificated Revocation checking as it could not obtain a valid OCSP Response to use from the CA OCSP responder. Details: Error:  not found in AuthorityInfoAccess"
  source.sql" 

Steps to Reproduce

Run sources with snowflake

Logs

No response

System Info

No response

Severity

serious, but I can work around it

Additional Information, or Workarounds

No response

@mcrascal mcrascal added bug Something isn't working connectors Database connectors to-review Evidence team to review labels Sep 12, 2024
@mcrascal mcrascal changed the title [Bug]: Snowflake OCSP based Certificated Revocation checking warnings [Bug]: Snowflake OCSP based Certificated Revocation Logs Sep 12, 2024
@archiewood
Copy link
Member

archiewood commented Oct 8, 2024

I have investigated somewhat here.

Snowlake claim to have fixed this as of v1.6.21,

snowflakedb/snowflake-connector-nodejs#457

but we are at 1.9.0 and still getting the warnings

I am able to upgrade to 1.9.3, and the warnings are still appearing

However, unable to upgrade >1.10.0 because there appears to be some kind of breaking change

(but nothing mentioned in the release notes)

Unable to perform operation because a connection was never established.

Latest is 1.14.X, which also cannot upgrade to, for the same reason as 1.10.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working connectors Database connectors to-review Evidence team to review
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants