-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ADAP-881] Dbt Version 1.6.1 Not Able to Authenticate with Snowflake via Private Key Config #767
Comments
Thanks for reaching out @chris-leigh-dignifi ! If you use a Base64-encoded DER #671 added the ability to use the PEM format with a Based on the Snowflake's instructions you linked to, it sounds like you are trying to use the PEM format? If so, then you'll have to use |
@dbeatty10 thank you for the quick response! Yes that's correct -- I am using PEM format for my key generation. Do you happen to have any instructions on converting the private key to Base64-encoded DER format via the command line? I tried following these instructions, but did not have any luck. |
Sure thing @chris-leigh-dignifi ! Unfortunately, I don't happen to have a set of instructions to do that conversion, and I haven't done that before personally. In the meantime, I'm going to close this in favor of #671 which should be released and available by the end of October. |
Is this a new bug in dbt-snowflake?
Current Behavior
I am able to successfully authenticate via the
private_key_path
, but when supplying the exact same key via a string using theprivate_key
config inprofiles.yaml
, dbt is not able to authenticate with Snowflake. I am using an encrypted private key and currently running dbt version 1.6.1.Expected Behavior
I expect dbt to be able to authenticate with Snowflake via either configuration options.
Steps To Reproduce
profiles.yaml
fileTest 1
private_key_path
config, confirm this method worksprivate_key
config, confirm that this method does not workRelevant log output
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: