- \n
- A JumpCloud administrator account<\/li>\n\n\n\n
- JumpCloud SSO Package or higher or SSO \u00e0 la carte option<\/li>\n\n\n\n
- A Snowflake user account with administrative permissions<\/li>\n\n\n\n
- Snowflake account-name\/alias<\/a><\/li>\n\n\n\n
- If you have an existing SSO implementation that uses the deprecated SAML_IDENTITY_PROVIDER<\/strong> account parameter, you must migrate to a SAML2 security integration<\/a> before continuing to configure Snowflake for federated authentication<\/li>\n<\/ul>\n\n\n\n
SCIM Important Considerations<\/strong><\/p>\n\n\n\n
- \n
- SSO is recommended, but not required for SCIM<\/li>\n\n\n\n
- 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<\/li>\n\n\n\n
- The access token is valid for six months. When you need to update your token, you must deactivate the IdM integration<\/a>, update the token, and then reactivate the IdM integration<\/li>\n\n\n\n
- List of users is not supported<\/li>\n\n\n\n
- 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)<\/li>\n<\/ul>\n\n\n\n
Attribute Considerations<\/strong><\/p>\n\n\n\n
- \n
- A default set of attributes are managed for users. See the Attribute Mappings<\/a> section for more details<\/li>\n\n\n\n
- Filter by email <\/kbd>is not supported (use userName<\/kbd> instead)<\/li>\n\n\n\n
- Groups are supported<\/li>\n<\/ul>\n\n\n\n
Creating a new JumpCloud Application Integration<\/strong><\/h2>\n\n\n\n
- \n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to\u00a0USER AUTHENTICATION\u00a0<\/strong>>\u00a0SSO<\/strong> Applications<\/strong>.<\/li>\n\n\n\n
- Click + Add New Application<\/strong>.<\/li>\n\n\n\n
- Type the name of the application in the Search <\/strong>field and select it.<\/li>\n\n\n\n
- Click Next<\/strong>.<\/li>\n\n\n\n
- In the Display Label<\/strong>, type your name for the application. Optionally, you can enter a Description<\/strong>, adjust the User Portal Image and choose to hide or Show in User Portal<\/strong>.<\/li>\n<\/ol>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\")
<\/p><\/div>Note:<\/strong> \nIf this is a Bookmark Application, enter your sign-in URL in the Bookmark URL<\/strong> field.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Optionally, expand Advanced Settings<\/strong> to specify a value for the SSO IdP URL<\/strong>. If no value is entered, it will default to https:\/\/sso.jumpcloud.com\/saml2\/<applicationname><\/kbd>.<\/li>\n<\/ol>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\")
<\/p><\/div>Warning:<\/strong> \nThe SSO IdP URL<\/strong> is not editable after the application is created. You will have to delete and recreate the connector if you need to edit this field at a later time.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Click Save Application<\/strong>.<\/li>\n\n\n\n
- If successful, click:\n
- \n
- Configure Application<\/strong> and go to the next section <\/li>\n\n\n\n
- Close<\/strong> to configure your new application at a later time <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
Configuring the SSO Integration<\/strong><\/h2>\n\n\n\n
To configure JumpCloud<\/strong><\/h3>\n\n\n\n
- \n
- Create a new application<\/a> or select it from the Configured Applications<\/strong> list.<\/li>\n\n\n\n
- Select the SSO <\/strong>tab.<\/li>\n\n\n\n
- Replace any instances of ACCOUNT_NAME with your Snowflake account name.<\/li>\n\n\n\n
- Add or change any attributes.<\/li>\n\n\n\n
- Click save<\/strong>.<\/li>\n<\/ol>\n\n\n\n
Download the certificate<\/strong><\/h4>\n\n\n\n
- \n
- Find your application in the Configured Applications<\/strong> list and click anywhere in the row to reopen its configuration window.<\/li>\n\n\n\n
- Select the SSO <\/strong>tab and click IDP Certificate Valid > Download certificate<\/strong>.<\/li>\n<\/ol>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/tip-icon.png\")
<\/p><\/div>Tip:<\/strong> \nThe certificate.pem will download to your local Downloads<\/strong> folder.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
To configure Snowflake<\/strong><\/h3>\n\n\n\n
- \n
- Log into your Snowflake account.<\/li>\n\n\n\n
- As a user with the ACCOUNTADMIN<\/strong> role, run the CREATE SECURITY INTEGRATION<\/kbd><\/a> command. The following example sets up JumpCloud SSO using the required parameters<\/a>:<\/li>\n<\/ol>\n\n\n\n\n
CREATE SECURITY INTEGRATION JUMPCLOUD
TYPE = SAML2
ENABLED = TRUE
SAML2_ISSUER = ‘<JUMPCLOUD ENTITY ID>’
SAML2_SSO_URL = ‘<JUMPCLOUD IDP URL>’
SAML2_PROVIDER = CUSTOM
SAML2_X509_CERT = ‘<CONTENTS OF JUMPCLOUD SSO CERTIFICATE>’ <\/p>\n<\/div><\/div>\n\n\n\n![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/important-icon.png\")
<\/p><\/div>Important:<\/strong> \nDo not include the leading —–BEGIN CERTIFICATE—–<\/kbd> and ending —–END CERTIFICATE—–<\/kbd> markers when copying the certificate’s contents into the above command.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- The following optional parameters<\/a> can be added to the CREATE SECURITY INTEGRATION<\/a><\/kbd> command:<\/li>\n<\/ol>\n\n\n\n\n
[ ALLOWED_USER_DOMAINS = ( ” [ , ” , \u2026 ] ) ]
[ ALLOWED_EMAIL_PATTERNS = ( ” [ , ” , \u2026 ] ) ]
[ SAML2_SP_INITIATED_LOGIN_PAGE_LABEL = ” ]
[ SAML2_ENABLE_SP_INITIATED = TRUE | FALSE ]
[ SAML2_SNOWFLAKE_X509_CERT = ” ]
[ SAML2_SIGN_REQUEST = TRUE | FALSE ]
[ SAML2_REQUESTED_NAMEID_FORMAT = ” ]
[ SAML2_POST_LOGOUT_REDIRECT_URL = ” ]
[ SAML2_FORCE_AUTHN = TRUE | FALSE ]
[ SAML2_SNOWFLAKE_ISSUER_URL = ” ]
[ SAML2_SNOWFLAKE_ACS_URL = ” ]
[ COMMENT = ” ]<\/p>\n<\/div><\/div>\n\n\n\nAuthorizing User SSO Access<\/strong><\/h2>\n\n\n\n
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<\/strong> panel or from the Groups Configuration<\/strong> panel. <\/p>\n\n\n\n
To authorize user access from the Application Configuration panel<\/strong><\/h3>\n\n\n\n
- \n
- Log in to the <\/a>JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to USER AUTHENTICATION > SSO<\/strong> Applications<\/strong>, then select the application to which you want to authorize user access.<\/li>\n\n\n\n
- Select the User Groups<\/strong> tab. If you need to create a new group of users, see Get Started: User Groups<\/a>.<\/li>\n\n\n\n
- Select the check box next to the group of users you want to give access.<\/li>\n\n\n\n
- Click save<\/strong>. <\/li>\n<\/ol>\n\n\n\n
To learn how to authorize user access from the Groups Configuration<\/strong> panel, see Authorize Users to an SSO Application<\/a>.<\/p>\n\n\n\n
Validating SSO user authentication workflow(s)<\/strong><\/h2>\n\n\n\n
IdP-initiated<\/strong> user workflow<\/strong><\/h3>\n\n\n\n
- \n
- Access the JumpCloud User Console<\/a><\/li>\n\n\n\n
- Go to\u00a0Applications<\/strong> and click an application tile to launch it<\/li>\n\n\n\n
- JumpCloud asserts the user’s identity to the SP and is authenticated without the user having to log in to the application<\/li>\n<\/ul>\n\n\n\n
SP-initiated<\/strong> user workflow<\/strong><\/h3>\n\n\n\n
- \n
- Go\u00a0to the SP application login – generally, there is either a special link or an adaptive username field that detects the user is authenticated through SSO<\/li>\n<\/ul>\n\n\n\n<\/p><\/div>Note:<\/strong> \n
This varies by SP.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Login redirects the user to JumpCloud where the user enters their JumpCloud credentials<\/li>\n\n\n\n
- After the user is logged in successfully, they are redirected\u00a0back to the SP and automatically logged in<\/li>\n<\/ul>\n\n\n\n
Configuring the Identity Management Integration<\/strong><\/h2>\n\n\n\n
To configure Snowflake<\/strong><\/h3>\n\n\n\n
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. <\/p>\n\n\n\n
- \n
- Log into your Snowflake account.<\/li>\n\n\n\n
- As a user with the ACCOUNTADMIN<\/strong> role, run the CREATE SECURITY INTEGRATION<\/kbd><\/a> statement using the required parameters<\/a>:<\/li>\n<\/ol>\n\n\n\n\n
CREATE SECURITY INTEGRATION <SCIM_INTEGRATION_NAME>
TYPE = SCIM
ENABLED = TRUE
SCIM_CLIENT = ‘GENERIC’
RUN_AS_ROLE = ‘GENERIC_SCIM_PROVISIONER’<\/p>\n<\/div><\/div>\n\n\n\n- \n
- The following optional parameters<\/a> can be added to the CREATE SECURITY INTEGRATION<\/a><\/kbd> command:<\/li>\n<\/ol>\n\n\n\n\n
[ NETWORK_POLICY = ” ]
[ SYNC_PASSWORD = { TRUE | FALSE } ]
[ COMMENT = ” ]<\/p>\n<\/div><\/div>\n\n\n\n- \n
- Create a token for the SCIM integration using SYSTEM$GENERATE_SCIM_ACCESS_TOKEN<\/kbd><\/a>. <\/li>\n<\/ol>\n\n\n\n\n
SYSTEM$GENERATE_SCIM_ACCESS_TOKEN(‘<SCIM_INTEGRATION_NAME>’)<\/p>\n<\/div><\/div>\n\n\n\n
<\/p><\/div>Note:<\/strong> \nThe access token is valid for six months. To continue using SCIM with Snowflake, recreate the SCIM integration with a CREATE SECURITY INTEGRATION<\/kbd><\/a> statement and generate a new access token using SYSTEM$GENERATE_SCIM_ACCESS_TOKEN<\/kbd><\/a>.<\/p>\n\n\n\n
To invalidate an existing access token for a SCIM integration, execute a DROP INTEGRATION<\/kbd><\/a> statement.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Managing SCIM Network Policies<\/strong><\/h4>\n\n\n\n
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.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
After creating the SCIM security integration, create the SCIM network policy using ALTER SECURITY INTEGRATION<\/kbd><\/a>:<\/p>\n\n\n\n
\nALTER SECURITY INTEGRATION <SCIM_INTEGRATION_NAME> SET NETWORK_POLICY =<\/kbd> <SCIM_NETWORK_POLICY>;<\/kbd><\/p>\n<\/div><\/div>\n\n\n\n
Where:<\/p>\n\n\n\n
- \n
- <SCIM_INTEGRATION_NAME><\/kbd> – specifies the name of the Custom SCIM security integration.<\/li>\n\n\n\n
- <SCIM_NETWORK_POLICY><\/kbd> – specifies the Custom SCIM network policy in Snowflake.<\/li>\n<\/ul>\n\n\n\n
<\/p><\/div>Note:<\/strong> \nFor more information, see Network Policies<\/a> and ALTER SECURITY INTEGRATION<\/kbd><\/a>.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Using Secondary Roles with SCIM<\/strong><\/h4>\n\n\n\n
Snowflake supports setting the user<\/a> property DEFAULT_SECONDARY_ROLES<\/kbd> to ‘ALL’<\/kbd> with SCIM to allow users to use secondary roles<\/a> in a Snowflake session.<\/p>\n\n\n\n
For a representative example, see Update a user<\/a>.<\/p>\n\n\n\n
Replicating the Custom SCIM Security Integration<\/strong><\/h4>\n\n\n\n
Snowflake supports replication and failover\/failback with the SCIM security integration from the source account to the target account.<\/p>\n\n\n\n
For details, see Replication of Security Integrations & Network Policies Across Multiple Accounts<\/a>.<\/p>\n\n\n\n
To configure JumpCloud<\/strong><\/h3>\n\n\n\n
- <SCIM_NETWORK_POLICY><\/kbd> – specifies the Custom SCIM network policy in Snowflake.<\/li>\n<\/ul>\n\n\n\n
- <SCIM_INTEGRATION_NAME><\/kbd> – specifies the name of the Custom SCIM security integration.<\/li>\n\n\n\n
- Create a token for the SCIM integration using SYSTEM$GENERATE_SCIM_ACCESS_TOKEN<\/kbd><\/a>. <\/li>\n<\/ol>\n\n\n\n
- The following optional parameters<\/a> can be added to the CREATE SECURITY INTEGRATION<\/a><\/kbd> command:<\/li>\n<\/ol>\n\n\n\n
- Go to\u00a0Applications<\/strong> and click an application tile to launch it<\/li>\n\n\n\n
- Go to USER AUTHENTICATION > SSO<\/strong> Applications<\/strong>, then select the application to which you want to authorize user access.<\/li>\n\n\n\n
- Log in to the <\/a>JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- The following optional parameters<\/a> can be added to the CREATE SECURITY INTEGRATION<\/a><\/kbd> command:<\/li>\n<\/ol>\n\n\n\n
- Select the SSO <\/strong>tab and click IDP Certificate Valid > Download certificate<\/strong>.<\/li>\n<\/ol>\n\n\n\n
- Select the SSO <\/strong>tab.<\/li>\n\n\n\n
- Close<\/strong> to configure your new application at a later time <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
- If successful, click:\n
- Click Save Application<\/strong>.<\/li>\n\n\n\n
- Go to\u00a0USER AUTHENTICATION\u00a0<\/strong>>\u00a0SSO<\/strong> Applications<\/strong>.<\/li>\n\n\n\n
- Filter by email <\/kbd>is not supported (use userName<\/kbd> instead)<\/li>\n\n\n\n
- If you have an existing SSO implementation that uses the deprecated SAML_IDENTITY_PROVIDER<\/strong> account parameter, you must migrate to a SAML2 security integration<\/a> before continuing to configure Snowflake for federated authentication<\/li>\n<\/ul>\n\n\n\n