This is an updated and improved version of the Snowflake connector! If you’re setting up Snowflake with ConductorOne for the first time, you’re in the right place.

Capabilities

• Sync user identities from Snowflake to ConductorOne

• Resources supported:

  • Account roles
  • Databases

• Provisioning supported:

  • Account roles to users

Add a new Snowflake connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

1. In ConductorOne, click Connectors > Add connector.

2. Search for Snowflake v2 and click Add.

   Don’t see the Snowflake v2 connector? Reach out to support@conductorone.com to add Snowflake v2 to your Connectors page.

3. Choose how to set up the new Snowflake connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

   Do you SSO into Snowflake using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged Snowflake app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   A Snowflake connector owner must have the following permissions:

   • Connector Administrator or Super Administrator role in ConductorOne
   • Manage Grants global privilege in Snowflake

5. Click Next.

Next steps

• If you are the connector owner, proceed to Configure your Snowflake connector for instructions on integrating Snowflake with ConductorOne.

• If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your Snowflake connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and Manage Grants global privilege in Snowflake must perform this task.

For best results, use a dedicated service account. ConductorOne will use the DEFAULT_WAREHOUSE, DEFAULT_NAMESPACE, and DEFAULT_ROLE properties of the user used for the integration. For this reason, we recommend creating a dedicated service account in Snowflake for integrating with ConductorOne with these default user properties.

Step 1: Generate a private key and set the public key on a Snowflake user

1. Generate an unencrypted private key in PEM format by running the following command:

   openssl genrsa 2048 | openssl pkcs8 -topk8 -inform PEM -out rsa_key.p8 -nocrypt
   

2. Next, use the private key to generate the public key. Run the following command:

   openssl rsa -in rsa_key.p8 -pubout -out rsa_key.pub
   

3. To enable public key authentication for a Snowflake user, execute the following ALTER USER command. You must have the ACCOUNTADMIN role to perform this operation:

   ALTER USER <SNOWFLAKEUSER> SET RSA_PUBLIC_KEY='MIIBIj...';
   

   Tip: When setting the RSA_PUBLIC_KEY, extract the key content between the -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- lines from your public key file. Do not include the header or footer. The key should be a single continuous string.

4. Carefully save the private key. We’ll use it in step 2.

Step 2: Add your Snowflake credentials to ConductorOne

1. In ConductorOne, navigate to the Snowflake connector by either:

   • Clicking the Set up connector link in the email you received about configuring the connector.

   • Navigate to Connectors > Snowflake v2 (if there is more than one Snowflake v2 listed, click the one with your name listed as owner and the status Not connected).

2. Find the Settings area of the page and click Edit.

3. In the Account URL field, enter the URL of your Snowflake instance, which is in the form <organization name>-<account name>. snowflakecomputing.org.

4. In the Account ID / Locator field, enter your Snowflake account identifier.

   Find your account identifier by navigating in the Snowflake console to your account, selecting your user, and finding the alphanumeric code listed under Locator.

5. In the Username field, enter your Snowflake username.

6. In the RSA Private Key (PEM Format) field, upload the private key file you generated in Step 1.

7. Click Save.

8. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Snowflake connector is now pulling access data into ConductorOne.

Configure the Snowflake integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between Snowflake and ConductorOne.

See the ConductorOne Snowflake v2 integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Troubleshooting the Snowflake v2 connector

If you’re seeing a 422 unprocessible entity or 401 unauthorized error in the logs, make sure that your service account has the DEFAULT_WAREHOUSEproperty, and that you’ve correctly looked up your Snowflake account identifier.