Configure Snowsight Cloud
Last modified on June 30, 2023
This guide explains how to connect Snowsight, Snowflake’s administrative user interface, as a cloud resource to StrongDM. Note that the configuration allows single sign-on (SSO).
- For the configuration to work, you must be able to connect to your Snowflake interface via SnowSQL. An admin or web interface does not work.
- Due to the limitations of this resource type, StrongDM does not log user interactions after authentication occurs. StrongDM logs activities such as setup or modification of the resource within StrongDM, or authentication of a user to the resource, but StrongDM does not log the queries performed by the user on the resource itself. We recommend the use of the Snowsight Activity area for logging further interactions with the resource once a user is authenticated.
- Similarly, some organization-level behaviors are also different for this resource type:
- Inactivity timeouts are not enforced.
- Current connections to resources are not severed instantly when access is revoked.
- StrongDM must be the only identity provider (IdP) configured for authentication to this resource.
- Before enabling this resource, ensure the Login Name for each Snowflake user (that is, not Username or Email) is set to match a StrongDM email. An email address serves as the ID StrongDM sends to Snowflake to log in a user. The following process disables identity provider (IdP) logins via any other method. Password logins still work.
- We recommend that you reach out to Snowflake support and request that users are not allowed to change their own passwords. Otherwise, once a user logs in to Snowflake via StrongDM, they may change their password and retain access to Snowflake even after their access is revoked in StrongDM.
Get StrongDM’s IdP Metadata
StrongDM’s IdP metadata is required for creating an integration account with Snowsight.
- Go to
app.strongdm.com/saml/idp_metadata. This is a public URL that returns a XML blob. Within this output, note the value of the X509Certificate. The value is present twice. Both instances should have the same value.
- Copy the certificate value and proceed to the next step.
Create a StrongDM Integration Account
This integration account sets StrongDM information, including the IdP certificate.
Note your Snowflake account name, which is also the account locator. One way to view your account name is to look at the web interface login URL, which you can find by navigating to
app.snowflake.comand then picking your login account. A URL similar to the following displays, where abc12345 is the account name:
In SnowSQL, execute the following command, being sure to replace the placeholders with your own values (for example, replace
create security integration strongdm_idp type = saml2 enabled = true saml2_issuer = 'https://app.strongdm.com/saml/idp_metadata' saml2_sso_url = '<ANY_STRING_IN_URL_FORMAT>' saml2_provider = 'Custom' saml2_x509_cert='<STRONGDM_IDP_X509_CERTIFICATE>' saml2_sp_initiated_login_page_label = '<ANY_STRING>' saml2_enable_sp_initiated = true saml2_force_authn = false saml2_requested_nameid_format = 'urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified' saml2_snowflake_issuer_url = 'https://<ACCOUNT_NAME>.snowflakecomputing.com' saml2_snowflake_acs_url = 'https://<ACCOUNT_NAME>.snowflakecomputing.com/fed/login';
Ensure that the metadata matches your base URL (for example,
https://<ACCOUNT_NAME>.snowflakecomputing.com). If you run into 403 errors when adding Snowsight as a cloud resource, it is likely because the wrong URL is set in the
Get the Snowsight Metadata XML Blob
The Snowsight metadata XML blob allows connection to StrongDM.
desc security integration strongdm_idp;in SnowSQL.
- Take the
SAML2_SNOWFLAKE_METADATAvalue and copy it for the resource configured in the following step.
Configure the Snowsight Cloud Resource
When you configure this cloud resource in the Admin UI, you use the Snowsight metadata XML blob to allow connection between Snowsight and StrongDM.
- Log into the Admin UI.
- Go to Infrastructure > Clouds.
- Click the Add cloud button.
- Select Snowsight (Snowflake Web Console) as the Cloud Type and set the other resource properties.
After configuration is complete, you can access a Snowsight resource using StrongDM. Note that when you do, you must use the Snowsight web interface, not the Snowflake classic web interface. You cannot switch to the Snowflake classic web interface.
Moreover, the first time that you access this resource, you may be presented with an option to use either Snowsight or the Snowflake classic web interface. You must choose Snowsight or else you won’t be able to switch to Snowsight later without admin help.
Configuration properties are visible when you add a cloud resource or when you click to view its settings. The following table describes the settings available for Snowsight (Snowflake Web Console).
|Display Name||Required||Meaningful name to display the resource throughout StrongDM; exclude special characters like quotes (") or angle brackets (< or >)|
|Datasource Type||Required||Select Snowsight (Snowflake Web Console)|
|Secret Store||Optional||Credential store location; defaults to Strong Vault; learn more about Secret Store options|
|SAML Metadata||Required||Metadata XML blob from your Snowflake IdP integration|
|Healthcheck Username||Required||In order for healthchecks to be successful, must be the email of a StrongDM user who has access to this resource, and must also match your Snowflake Login Name (that is, not Username or Email)|
|Subdomain||Required||Value to use for your local DNS address (for example, |
|Resource Tags||Optional||Datasource tags consisting of key-value pairs |
Secret store options
By default, resource credentials are stored in the Strong Vault. However, these credentials also can be saved in a third-party secrets management tool.
Non-StrongDM options appear in the Secret Store dropdown if they are created under Network > Secret Stores. When you select another Secret Store type, its unique properties display. For more details, see Configure Secret Store Integrations.
If any errors occur, please contact email@example.com.