Snowflake supports the SAML 2.0 protocol for federated authentication, allowing organizations to use their existing identity provider (IdP), such as Okta, to authenticate users. We’ve seen many organizations use the Snowflake and Okta combo to simplify user management and authentication to their Snowflake account. In this guide, we’ll show you how to create an Okta application for your Satori-protected Snowflake account.
When protecting a Snowflake data store with Satori, clients should use the Satori-generated hostname instead of the *.snowflakecomputing.com hostname. However, the default Okta application for Snowflake does not allow the hostname it redirects to after authentication to be changed. We recommend creating a custom SAML 2.0 Okta application to overcome this. This guide provides step-by-step instructions on how to do this.
Before we begin, you will need to ensure that you have the appropriate permissions to do the following:
- Add a new application in Okta
- ACCOUNTADMIN or SECURITYADMIN role in Snowflake
