Issue with asn1crypto==1.0.1 while connecting to Snowflake

[AzisK]

I get an error with asn1crypto==1.0.1 while connecting to Snowflake. The error stacktrace is huge and I may not share everything due to confidentiality but I am sharing its first / last and most important parts. I am getting this.

ERROR:snowflake.connector.network: 'APIException' object has no attribute 'message'
INFO - Traceback (most recent call last):
INFO -   File "/disk2/seo/seo-etls/.venv/lib/python3.6/site-packages/snowflake/connector/ocsp_snowflake.py", line 1065, in validate_by_direct_connection
INFO -     self.process_ocsp_response(issuer, cert_id, ocsp_response)
INFO -   File "/disk2/seo/seo-etls/.venv/lib/python3.6/site-packages/snowflake/connector/ocsp_asn1crypto.py", line 276, in process_ocsp_response
INFO -     tbs_response_data)
INFO -   File "/disk2/seo/seo-etls/.venv/lib/python3.6/site-packages/snowflake/connector/ocsp_asn1crypto.py", line 303, in verify_signature
INFO -     pubkey = cert.public_key.unwrap().dump()
INFO -   File "/disk2/seo/seo-etls/.venv/lib/python3.6/site-packages/asn1crypto/keys.py", line 1064, in unwrap
INFO -     'asn1crypto.keys.PublicKeyInfo().unwrap() has been removed, '
INFO - asn1crypto._errors.APIException: asn1crypto.keys.PublicKeyInfo().unwrap() has been removed, please use oscrypto.asymmetric.PublicKey().unwrap() instead

snowflake.connector.errors.OperationalError: 250003: Failed to execute request: 'APIException' object has no attribute 'message'

However, asn1crypto==0.24.0 works well!

[wbond]

asn1crypto 1.0.0 was a breaking change. My guess is that the snowflake spec for asn1crypto specified >= 0.24.0, whereas it should probably have been limited to >= 0.24.0 and < 1.0.0.

I think #154 was an issue about this from someone involved with the snowflake project.

[smtakeda]

Sorry about inconvenience. The patch including <1.0.0 was out in Snowflake Python Connector 1.9.1 and 2.0.1. and the fix including <1.1.0 will be out next week.

[wbond]

No problem on my end.

Just so you know, this project strives to follow SemVer, so if I introduce any future breaking changes, there will be a 2.0.0. I will be cutting a 1.2.0 soon since I am adding a new feature that provide load order info to allow hot-reloading of the code.