Field Notice: Upcoming changes to Snowflake connection authentication
What is changing?
Snowflake is transitioning away from password-only authentication to a secure by default behavior for new Snowflake accounts. This change will deliver stronger protection for authentication across all Snowflake services.
Although the password-only authentication will be supported by Snowflake for existing accounts for some time, we strongly advise updating your username and password authentication to Key-pair authentication as soon as possible.
Who is impacted?
Metadata collection: Only the Snowflake collectors using the Username and password authentication are impacted. If you are already using Username and Key-pair authentication for your collectors, no action is required.
Virtualization connections: Only the Snowflake connections using the Username and password authentication are impacted. If you are already using Username and Key-pair authentication for your connections, no action is required.
Action required for metadata collectors
Follow these steps to configure Username and Key-pair authentication in Snowflake.
Update your collector configuration to use the Username and Key pair authentication.
If you are using Cloud collectors, update the collector configuration to use Authenticate using a private key file.
If you are using On-premise collectors, update the collector configuration to use Authenticate using a private key file. Next, update the CLI command and YAML file to use new authentication parameters.
Run your collector to make sure the authentication for the collector is configured properly.
Action required for virtualization connections
Configure Username and Key-pair authentication in Snowflake.
Update the Snowflake configuration in the Connection Manager to use the Connection private key authentication.
Test your connection to make sure the authentication for the connection is configured properly.
Support
Please contact data.world support team for further assistance.