hasura / hasura/graphql-engine

Support: Add Encrypted Key Support to Snowflake Connector

Open
#10,115 2 comments 1 reaction 0 assignees View on GitHub
k/enhancement
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Is your proposal related to a problem?

Currently, [snowflake connector](https://hasura.io/docs/latest/databases/snowflake/getting-started/cloud/) only provides support for non-encrypted keys not encrypted keys.

### Describe the solution you'd like

As per this snowflake [doc](https://docs.snowflake.com/en/developer-guide/jdbc/jdbc-configure#privatekey-property-in-connection-properties), it provides private key support with p8 file access. So essentially, user can pass a file path to their private key file with encrypted key(p8) and passphrase alongside.

Support for this in Hasura would be crucial in case where user is looking to pass encrypted key file (p8) path as private key alongside passphrase for encrypted key.

Contributor guide

Open the contributing guide

Research direction

Start with the Snowflake connector configuration described in the issue and compare its current private-key handling with Snowflake's JDBC privatekey-property documentation. Done means users can provide a p8 private-key path and passphrase for encrypted keys, with connector coverage validating the configuration.

Written by the indexing model from the issue text.

Assessment

Domain
database
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.