Support Key Pair authentication for Snowflake destination

[grishick]

Tell us about the problem you're trying to solve

Currently for our snowflake destination we only support authentication via username and password but snowflake supports other forms of authentication as well.
Ref : https://docs.snowflake.com/en/user-guide/authentication.html

Describe the solution you’d like

A user should be able to use key pair authentication for Snowflake destination connector. More info here: https://docs.snowflake.com/en/user-guide/key-pair-auth.html

Describe the alternative you’ve considered or used

The alternative is to use username/password authentication

┆Issue is synchronized with this Asana task by Unito

[bashyroger]

We need this too, as we are obliged to have MFA on in snowflake. Only by using key pair authentication can we mitigate the issue of unwanted MFA popups when using airbyte based Snowflake target connectors.

[etsybaev]

This ticket partially clones https://app.zenhub.com/workspaces/java-connectors-625f0102b11304001e0f6c6e/issues/airbytehq/airbyte/6588

[sashaNeshcheret]

In scope of the ticket we need to:

• create private/public keys;
• add it to snowflake user;
• add toggle for username/password or private/public key authentication;
• create file with key for openssl;
• handle private/public key for jdbc;
• add integration test for it.

[sashaNeshcheret]

@grishick do we need to create the same ticket for snowflake source?

[grishick]

@grishick do we need to create the same ticket for snowflake source?

Yes, please create a separate ticket for the source