You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not too long ago, the JDBC driver enabled a parameter called private_key_base64 (https://docs.snowflake.com/en/developer-guide/jdbc/jdbc-parameters#private-key-base64) to pass a key directly via parameter, not requiring a PEM file. As far as I can tell from experimenting and looking at the code, this isn't supported by snowflake-connector-python in any way.
What is the desired behavior?
Just like passing private_key to the connector right now, passing private_key_base64 should be a supported option.
How would this improve snowflake-connector-python?
Feature parity (at least in this aspect) with JDBC; reduces the initial barrier for setting up a connection.
References and other background
No response
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Support authentication via private_key_base64
SNOW-1858462: Support authentication via private_key_base64
Dec 16, 2024
What is the current behavior?
Not too long ago, the JDBC driver enabled a parameter called private_key_base64 (https://docs.snowflake.com/en/developer-guide/jdbc/jdbc-parameters#private-key-base64) to pass a key directly via parameter, not requiring a PEM file. As far as I can tell from experimenting and looking at the code, this isn't supported by snowflake-connector-python in any way.
What is the desired behavior?
Just like passing private_key to the connector right now, passing private_key_base64 should be a supported option.
How would this improve
snowflake-connector-python
?Feature parity (at least in this aspect) with JDBC; reduces the initial barrier for setting up a connection.
References and other background
No response
The text was updated successfully, but these errors were encountered: