Open archiewood opened 1 month ago
(edit: edited your original submission and removed account-related and other possibly sensitive information from the log you provided. Which, by the way, (the logs and all the details + repro) is highly appreciated! )
hi and thank you for raising this issue. oid 1.3.6.1.5.5.7.48.1
in certificate Authority Information Access
is the oid for OCSP entry, which per this error message, is missing.
So let's verify.
$ export hostname="gcpuseast4-838400-stage.storage.googleapis.com"
$ echo | openssl s_client -showcerts -connect "$hostname":443 -servername "$hostname" 2>/dev/null | awk '/BEGIN/,/END/{ if(/BEGIN/){a++}; out="cert"a".pem"; print >out}'; for cert in cert*.pem; do echo "--> $cert"; openssl x509 -noout -subject -issuer -startdate -enddate -ocsp_uri -in $cert; echo; done
--> cert1.pem
subject=CN = *.storage.googleapis.com
issuer=C = US, O = Google Trust Services, CN = WR2
notBefore=Sep 16 09:29:09 2024 GMT
notAfter=Dec 9 09:29:08 2024 GMT
http://o.pki.goog/wr2
--> cert2.pem
subject=C = US, O = Google Trust Services, CN = WR2
issuer=C = US, O = Google Trust Services LLC, CN = GTS Root R1
notBefore=Dec 13 09:00:00 2023 GMT
notAfter=Feb 20 14:00:00 2029 GMT
--> cert3.pem
subject=C = US, O = Google Trust Services LLC, CN = GTS Root R1
issuer=C = BE, O = GlobalSign nv-sa, OU = Root CA, CN = GlobalSign Root CA
notBefore=Jun 19 00:00:42 2020 GMT
notAfter=Jan 28 00:00:42 2028 GMT
http://ocsp.pki.goog/gsr1
Indeed, the first intermediary CA cert (saved in cert2.pem
) does not have a OCSP URI. We already contacted Google a couple of weeks ago, and long story short, they don't want to fix it.
On the long term, we'll adapt all our drivers to how the world is changing and more and more CA's seem to move away from OCSP. On the short term, you can
insecureConnect: true
(which we, as Snowflake, generally don't really recommend to do as a permanent 'solution' but here the cert chain cannot fully be validated anyways, so...)On the short term, we're already considering some 'workaround' to adapt to this Google decision, like reword the warning, or stop emitting it by default.
So right now, it's expected to behave like this due to the cloud service provider changing their approach.
Thank you for your response, this is helpful!
If the account identifier is considered private information, it should probably be removed from the bug issue template!
working on it ;) https://github.com/snowflakedb/snowflake-connector-nodejs/pull/927
We are getting warning messages about OCSP Responses using the latest driver version. These are very noisy for our clients.
This happens in particular with larger queries, see my repro
Info
node --version
andnpm --version
)npm list
)?6.Server version:* E.g. 1.90.1
See minimal repro in this repository: https://github.com/archiewood/repro-snowflake-ocsp
No warning messages are printed