Integrate with Snowflake

Use JumpCloud SAML Single Sign On (SSO) to give your users convenient but secure access to all their web applications with a single set of credentials. Provision, update, and deprovision users in Snowflake in real-time from JumpCloud using the Identity Management (SCIM) integration. Leverage this integration for centralized and automated user lifecycle management and improved security related to user changes and user offboarding.

Read this article to learn how to configure the Snowflake integration.

Prerequisites

• A JumpCloud administrator account
• JumpCloud SSO Package or higher or SSO à la carte option
• A Snowflake user account with administrative permissions
• Snowflake account-name/alias
• If you have an existing SSO implementation that uses the deprecated SAML_IDENTITY_PROVIDER account parameter, you must migrate to a SAML2 security integration before continuing to configure Snowflake for federated authentication

SCIM Important Considerations

• SSO is recommended, but not required for SCIM
• If you deactivate the Identity Management on your Snowflake application, previously bound users remain active in Snowflake and able to authenticate using SSO. No further updates will be made to user accounts via the Identity Management integration
• The access token is valid for six months. When you need to update your token, you must deactivate the IdM integration, update the token, and then reactivate the IdM integration
• List of users is not supported
• Snowflake supports a maximum of 500 requests per account per SCIM endpoint. After your account exceeds this threshold, Snowflake returns a 429 HTTP status code (i.e. too many requests)

Attribute Considerations

• A default set of attributes are managed for users. See the Attribute Mappings section for more details
• Filter by email is not supported (use userName instead)
• Groups are supported

Creating a new JumpCloud Application Integration

1. Log in to the JumpCloud Admin Portal.
2. Navigate to USER AUTHENTICATION > SSO Applications.
3. Click + Add New Application.
4. Type the name of the application in the Search field and select it.
5. Click Next.
6. In the Display Label, type your name for the application. Optionally, you can enter a Description, adjust the User Portal Image and choose to hide or Show in User Portal.

7. Optionally, expand Advanced Settings to specify a value for the SSO IdP URL. If no value is entered, it will default to https://sso.jumpcloud.com/saml2/<applicationname>.

8. Click Save Application.
9. If successful, click:
   • Configure Application and go to the next section
   • Close to configure your new application at a later time

Configuring the SSO Integration

To configure JumpCloud

1. Create a new application or select it from the Configured Applications list.
2. Select the SSO tab.
3. Replace any instances of ACCOUNT_NAME with your Snowflake account name.
4. Add or change any attributes.
5. Click save.

Download the certificate

1. Find your application in the Configured Applications list and click anywhere in the row to reopen its configuration window.
2. Select the SSO tab and click IDP Certificate Valid > Download certificate.

To configure Snowflake

1. Log into your Snowflake account.
2. As a user with the ACCOUNTADMIN role, run the CREATE SECURITY INTEGRATION command. The following example sets up JumpCloud SSO using the required parameters:

3. The following optional parameters can be added to the CREATE SECURITY INTEGRATION command:

Authorizing User SSO Access

Users are implicitly denied access to applications. After you connect an application to JumpCloud, you need to authorize user access to that application. You can authorize user access from the Application Configuration panel or from the Groups Configuration panel. 

To authorize user access from the Application Configuration panel

1. Log in to the JumpCloud Admin Portal.
2. Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
3. Select the User Groups tab. If you need to create a new group of users, see Get Started: User Groups.
4. Select the check box next to the group of users you want to give access.
5. Click save. 

To learn how to authorize user access from the Groups Configuration panel, see Authorize Users to an SSO Application.

Validating SSO authentication workflow(s)

IdP-initiated

• Access the JumpCloud User Console
• Select the application’s tile
• The application will launch and login the user

SP-initiated

• Navigate to your Service Provider application URL
• You will be redirected to log in to the JumpCloud User Portal
• The browser will be redirected back to the application and be automatically logged in

Configuring the Identity Management Integration

To configure Snowflake

The Snowflake configuration process creates a SCIM security integration to allow users and roles created in the identity provider to be owned by the GENERIC_SCIM_PROVISIONER SCIM role in Snowflake and creates an access token to use in SCIM API requests.

1. Log into your Snowflake account.
2. As a user with the ACCOUNTADMIN role, run the CREATE SECURITY INTEGRATION statement using the required parameters:

3. The following optional parameters can be added to the CREATE SECURITY INTEGRATION command:

4. Create a token for the SCIM integration using SYSTEM$GENERATE_SCIM_ACCESS_TOKEN.

Managing SCIM Network Policies

The SCIM network policy has its own setting so that the SCIM provider can be specifically allowed to provision users and groups without adding these IP addresses for normal user access.

Setting up a network policy specific to the SCIM integration allows SCIM to be distinct from other network policies that may apply to the Snowflake account. The SCIM network policy does not affect other network policies on the account nor do other account network policies affect the SCIM network policy. Therefore, the SCIM network policy allows the Snowflake SCIM integration to provision users and groups as intended.

After creating the SCIM security integration, create the SCIM network policy using ALTER SECURITY INTEGRATION:

Where:

• <SCIM_INTEGRATION_NAME> – specifies the name of the Custom SCIM security integration.
• <SCIM_NETWORK_POLICY> – specifies the Custom SCIM network policy in Snowflake.

Using Secondary Roles with SCIM

Snowflake supports setting the user property DEFAULT_SECONDARY_ROLES to 'ALL' with SCIM to allow users to use secondary roles in a Snowflake session.

For a representative example, see Update a user.

Replicating the Custom SCIM Security Integration

Snowflake supports replication and failover/failback with the SCIM security integration from the source account to the target account.

For details, see Replication of Security Integrations & Network Policies Across Multiple Accounts.

To configure JumpCloud

1. Create a new application or select it from the Configured Applications list.
2. Select the Identity Management tab.
3. Click Configure to expand the Configuration Settings.
4. You’re presented with two fields:
   • Base URL: https://<account-name/alias>.snowflakecomputing.com/scim/v2
   • Token Key: Paste the authorization token generated in the previous section.
5. Click Activate.
6. If successful, click save.
7. You will receive a confirmation that the Identity Management integration has been successfully verified.

Attribute Mappings

The following table lists attributes that JumpCloud sends to the application. See Attribute Considerations for more information regarding attribute mapping considerations. 

Learn about JumpCloud Properties and how they work with system users in our API. 

Group Management Considerations

Enabling Group Management

You must select the Enable management of User Groups and Group Membership in this application option to manage groups and group membership in the application from JumpCloud.

Group Provisioning and Syncing 

• Empty groups are not created
• JumpCloud takes over management of existing groups in the application when the user group name in JumpCloud matches the name of the group in the application
• All user groups associated with the application in JumpCloud are synced. Syncing occurs whenever there is a membership or group change event
• Group renaming is supported
• If a user group is disassociated from the application in JumpCloud, syncing immediately stops and the group is left as-is in the application. All members of that user group are deactivated in the application unless they are associated with another active application group that is managed from JumpCloud

Group Deletion

• Managed groups deleted in JumpCloud are deleted in the application
• All members of the deleted group are deactivated in the application, unless they are associated with another active application group that is managed from JumpCloud

Disabling Group Management

• You can disable group and group membership management by unchecking the Enable management of User Groups and Group Membership in this application option
• The managed groups and group membership are left as-is in the application
• JumpCloud stops sending group membership information for the user, but the user’s identity will continue to be managed from JumpCloud

Importing Users

This functionality is helpful if users have already been created in the application but have not been created in JumpCloud.

1. Log in to the JumpCloud Admin Portal.
2. Go to USER AUTHENTICATION > SSO Applications.
3. Search for the application and click to open its configuration panel. 
4. Select the Identity Management tab.
5. Click manual import.
6. Select the users you want to create in JumpCloud from the application from the list of users that appear. Users in the list have two import statuses:
   • New – user has not been imported
   • Imported – user has been imported and has an account in JumpCloud

7. Click import.
   • If you are importing less than 100 users, your import results will display in real time and you can continue onboarding your users 
   • If you have more than 100 users being imported, JumpCloud will send you an email when your import is complete

8. You can now connect and grant users access to all their JumpCloud resources. Learn more in the Authorize Users to an Application and Connecting Users to Resources articles.

SCIM Directory Insights Events

The following Directory Insights (DI) events provide visibility into failures and detailed information about the user and group data being added or updated from HR or other external solutions to JumpCloud.

If SCIM Groups are supported:

Removing the Integration

To deactivate the IdM Integration

1. Log in to the JumpCloud Admin Portal.
2. Go to USER AUTHENTICATION > SSO Applications.
3. Search for the application that you’d like to deactivate and click to open its details panel. 
4. Under the company name and logo on the left hand panel, click the Deactivate IdM connection link.
5. Click confirm. 
6. If successful, you will receive a confirmation message.

To deactivate the SSO Integration or Bookmark

1. Log in to the JumpCloud Admin Portal.
2. Go to USER AUTHENTICATION > SSO Applications.
3. Search for the application that you’d like to deactivate and click to open its details panel. 
4. Select the SSO or Bookmark tab.
5. Scroll to the bottom of the configuration.
6. Click Deactivate SSO or Deactivate Bookmark. 
7. Click save. 
8. If successful, you will receive a confirmation message.

To delete the application

1. Log in to the JumpCloud Admin Portal.
2. Go to USER AUTHENTICATION > SSO Applications.
3. Search for the application that you’d like to delete.
4. Check the box next to the application to select it.
5. Click Delete.
6. Enter the number of the applications you are deleting
7. Click Delete Application.
8. If successful, you will see an application deletion confirmation notification.