Hope it works. @aehrenworth
I’ve just been reading around the issue of encrypted private keys on the DBeaver community site, where people have also had fun with snowflake.
The following setting, was introduced in the knime.ini file in the most recent version of KNIME:
-Dnet.snowflake.jdbc.enableBouncyCastle=true
5.4. changelog:
- AP-23511: Support OpenSSL V3 private keys in Snowflake Connector node by adding the Bouncy Castle JVM argument to knime.ini file
- AP-23114: Update Snowflake driver to version 3.20
Now from what I have gathered on the DBeaver site, is that this setting allows the Snowflake JDBC driver to use an encrypted private key file, but is only present in their driver version 3.16 and later (e.g. 3.20). The latest version of the snowflake driver present in KNIME 5.4 as can be seen from the changelog is 3.20, so it’s possible that encrypted private keys will work with that, and I shall try it at some point.
However I reverted to an earlier driver 3.14 (deprecated in 5.4) because of a reported problem with using DB Loader with Snowflake KNIME and the 3.20 driver .
This would explain why I am not seeing the encrypted private file working! As I say, I have yet to try using the 3.20 driver.
Which version of KNIME are you using, and which snowflake driver version?