erg opened a new issue, #58573:
URL: https://github.com/apache/airflow/issues/58573

   ### Apache Airflow version
   
   3.1.3
   
   ### If "Other Airflow 2/3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Looks like it's dying in openssl?
   
   I have this same .pem file loading in Airflow 2.10.3 with 
`apache-airflow-providers-snowflake==5.7.0` and it works. It's possible that my 
openssl is missing some features that it needs to load this private key? It's 
aws linux on ec2.
   
   ```
   [2025-11-21 15:19:26] INFO - Snowflake connection test failed: ('Could not 
deserialize key data. The data may be in an incorrect format, it may be 
encrypted with an unsupported algorithm, or it may be an unsupported key type 
(e.g. EC curves with explicit parameters).', [<OpenSSLError(code=503841036, 
lib=60, reason=524556, reason_text=unsupported)>]) 
source=unusual_prefix_265870fe9aeac5517b7f38b2a081d1e60a78a9d2_system_report_dag
 loc=system_report_dag.py:101
   ```
   
   ### What you think should happen instead?
   
   _No response_
   
   ### How to reproduce
   
   Copy/paste your creds into the Extra Fields JSON of the snowflake connector. 
I tried both the raw .pem format and the base64 version. Both have the above 
error. (Why doesn't it complain that my base64 doesn't decode?)
   
   I have also tried setting up the connections with the command line and get 
the same error.
   
   ```
   {"private_key_content":"-----BEGIN PRIVATE KEY-----\n...MEvgIB...a\n-----END 
PRIVATE KEY-----","warehouse":"GENERAL","account":"foobar.us-east-1"}
   
   
{"private_key_content":"LS0tLS1CRU...","warehouse":"GENERAL","account":"foobar.us-east-1"}
   ```
   
   ### Operating System
   
   Amazon Linux
   
   ### Versions of Apache Airflow Providers
   
     apache-airflow==3.1.3
     apache-airflow-core==3.1.3
     apache-airflow-providers-amazon==9.16.0
     apache-airflow-providers-celery==3.13.0
     apache-airflow-providers-cncf-kubernetes==10.9.0
     apache-airflow-providers-common-compat==1.8.0
     apache-airflow-providers-common-io==1.6.4
     apache-airflow-providers-common-messaging==2.0.0
     apache-airflow-providers-common-sql==1.28.2
     apache-airflow-providers-docker==4.4.4
     apache-airflow-providers-elasticsearch==6.3.4
     apache-airflow-providers-fab==3.0.1
     apache-airflow-providers-ftp==3.13.2
     apache-airflow-providers-git==0.0.9
     apache-airflow-providers-google==18.1.0
     apache-airflow-providers-grpc==3.8.2
     apache-airflow-providers-hashicorp==4.3.3
     apache-airflow-providers-http==5.4.0
     apache-airflow-providers-imap==3.9.3
     apache-airflow-providers-microsoft-azure==12.8.0
     apache-airflow-providers-microsoft-mssql==4.3.2
     apache-airflow-providers-mysql==6.3.4
     apache-airflow-providers-odbc==4.10.2
     apache-airflow-providers-openai==1.6.3
     apache-airflow-providers-openlineage==2.7.3
     apache-airflow-providers-opensearch==1.7.4
     apache-airflow-providers-postgres==6.4.0
     apache-airflow-providers-qdrant==1.4.3
     apache-airflow-providers-redis==4.3.2
     apache-airflow-providers-sendgrid==4.1.4
     apache-airflow-providers-sftp==5.4.1
     apache-airflow-providers-slack==9.4.0
     apache-airflow-providers-smtp==2.3.1
     apache-airflow-providers-snowflake==6.6.0
     apache-airflow-providers-sqlite==4.1.2
     apache-airflow-providers-ssh==4.1.5
     apache-airflow-providers-standard==1.9.1
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   `docker compose up`
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to