OAuth 2.0 Support added for the Snowflake Input Connector

5
(1)

Our team has had a ton of requests for adding more authentication modes to our connector stack and specifically for Snowflake. OAuth is a standard in the industry and we have chosen to adopt it for adding the next level of auth functionality. Let’s have a closer look at this addition to the Snowflake connector.

OAuth based Connector/Connection at a Glance

Some might see OAuth as a simple thing they consume when they login to a web app like Salesforce, but several integration points need to come together to make this seem so simple. I’ll illustrate below and via the accompanying video how these moving pieces come together.

We need to create a link between Okta, an identity platform, and Snowflake and then from Okta to Salesforce and then from Salesforce to CRM Analytics.

Please keep in mind that from a Salesforce side and a Snowflake side these components are fairly well defined and have documented requirements. On the other hand in the Okta and other potential authentication services providers, there is a bunch of variables in how things are configured. What we have identified here is a scenario based on core functionality, if your Okta Admin has things configured in special ways we (Salesforce) may not have the means to facilitate every configuration and variation of the available use cases. If you come across an issue, raise it up and we will discuss it with you; just keep in mind we aren’t the Okta experts.

Ok, the simple steps

1: Create the Authorization Server in Okta; connecting your Snowflake and Okta accounts.

2: Create the Okta Application to facilitate the connection between Okta and Salesforce.

3: Create the Snowflake Security Integration to integrate with Okta.

4: Create a Salesforce Auth. Provider to connect to the Okata Application and provide the callback URL.

5: Create a Salesforce Named Credential to leverage the Auth. Provider’s Okta integration and set Scope for the integration into Snowflake.

6: Place the Named Credential Name in the connection dialog in Salesforce Data Pipelines/CRM Analytics.

And that’s it. You are now ready to extract data and transform it using data prep.

How useful was this post?

Click on a star to rate useful the post is!

Written by


2 thoughts on “OAuth 2.0 Support added for the Snowflake Input Connector”

  • 1
    Corey C on March 15, 2024 Reply

    Thanks for the insight Chris. We are attempting to setup oAuth with CRMA and snowflake through Azure AD provider, and keep receiving this error [390303] Invalid OAuth access token. [7b2b24f1-6451-4aa1-b7f1-915af830ef86] Error in Job ID connector.4vnuuoSjHHVWk-l1cKfy9-:

    Have you ever experienced this and had a fix ? Since there is little insight into where the error is being thrown we are lost on what application is the issue (Salesforce named credential config? CRMA config? Snowflake?).

    • 2
      shridhar patankar on July 2, 2024 Reply

      I am facing the same issue Invalid OAuth access token with Snowflake Connector from CRMA.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.