ADF Snowflake New Connector Issues with KeyPair Authentication and Private Link

Datta, Vinay 10 Reputation points
2024-10-18T09:55:11.7766667+00:00

We are using Azure Data Factory (ADF) to connect to Snowflake with a Self-hosted Integration Runtime configured for Private Link. Recently, we migrated the Snowflake connector to the latest version that supports Key Pair authentication.

Currently, Basic authentication is set up using the account123.privatelink value in the Snowflake Account identifier field. However, switching to Key Pair authentication is not functioning as expected.

We are suspecting that the JWT token generated may be utilizing the .privatelink extension, leading to authentication failures on the Snowflake side. It works as expected when using the public link which we would like to avoid.

Any assistance would be greatly appreciated.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,639 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Ravikumar S Minajigi 0 Reputation points
    2025-04-01T09:24:34.1233333+00:00

    As per the instructions provided in the below link, we followed:
    https://docs.snowflake.com/en/user-guide/key-pair-auth

    Post creating the Private and Public Keys using the openssl tool commands, assigning the public key to the user in snowflake resolved the issue.

    Key things to remember: When creating the linked service for Snowflake, please provide valid account name in the below format:
    <myorg-account123>.snowflakecomputing.com

    Thanks,

    Ravi

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.