🔐 What changed

Stigg’s Snowflake integration now supports key pair authentication instead of username and password.
In this new flow, the public key is stored inside your Snowflake user configuration, and the private key is securely uploaded in Stigg.

This change ensures stronger security and aligns with Snowflake’s deprecation of username + password authentication.

💡 Why it matters

Snowflake is deprecating password-based authentication to strengthen account protection.
At Stigg, we have a deep sense for customer security and have therefore set key pair authentication as the default method for all new Snowflake integrations.

📦 Availability

• Default for all new Snowflake integrations.
• Existing customers can migrate to the new authentication method using the migration guide in our documentation.

⚙️ How to use it

1. Go to Integrations → Snowflake in your Stigg account.
   
   
   
2. Generate your key pair using the provided commands.
   
   
3. Add the public key to your Snowflake user configuration.
4. In Stigg, upload the private key (and optional passphrase) to connect.
   
   
5. To rotate keys later, upload a new private key and update the corresponding public key in Snowflake.

Full guide: Stigg documentation