← Cloudflare One / cloudflare-one / integrations / identity-providers
JumpCloud (SAML)
JumpCloud ↗ provides SSO identity management. Cloudflare Access integrates with JumpCloud as a SAML identity provider.
The following steps are specific to setting up JumpCloud with Cloudflare Access. For more information on configuring JumpCloud SSO application, refer to the JumpCloud documentation ↗.
Set up Jumpcloud as a SAML provider
1. Create an SSO application in JumpCloud
-
In the JumpCloud Admin Portal ↗, go to SSO Applications.
-
Select Add New Application.
-
In the search bar, enter
Cloudflareand select the Cloudflare Access application. -
Select Next.
-
In Display Label, enter an application name.
-
Select Save Application.
-
Review the application summary and select Configure Application.
-
In the SSO tab, configure the following settings:
-
In IdP Entity ID, enter your Cloudflare team domain:
https://<your-team-name>.cloudflareaccess.com/You can find your team name in the Cloudflare dashboard ↗ under Settings > Team name and domain > Team name.
-
Set both SP Entity ID and ACS URL to the following callback URL:
https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback -
(Optional) Configure SAML attributes that you want to send to Cloudflare Access.
-
Scroll up to JumpCloud Metadata and select Export Metadata. Save this XML file for use in a later step.
-
-
In the User Groups tab, assign user groups ↗ to this application.
-
Select Save.
2. Add JumpCloud to Cloudflare One
-
In the Cloudflare dashboard ↗, go to Zero Trust > Integrations > Identity providers.
-
Under Your identity providers, select Add new identity provider.
-
Select SAML.
-
Upload your JumpCloud XML metadata file.
-
(Optional) To enable SCIM, refer to Synchronize users and groups.
-
(Optional) Under Optional configurations, configure additional SAML options.
-
Select Save.
You can now test your connection and create Access policies based on the configured login method and SAML attributes.
Synchronize users and groups
The JumpCloud integration allows you to synchronize user groups and automatically deprovision users using SCIM.
SCIM affects Access and Gateway policy evaluation differently.
Access evaluates a user's identity and group membership from the SAML assertion or OIDC token returned by the identity provider during authentication. SCIM provides readable group names in the Access policy builder, but Access does not use SCIM group membership to evaluate a login. If you turn on Enable user deprovisioning, removing a user from the SCIM application revokes their active Access sessions. You can also configure SCIM to revoke sessions after group membership changes. Access evaluates the updated identity provider data when the user authenticates again.
Gateway evaluates identity-based policies against the User Registry identity. SCIM updates this identity when users or group memberships change, without waiting for the user to authenticate again. Cloudflare One Client device profiles use the same synchronized identity.
1. Enable SCIM in Cloudflare One
-
In the Cloudflare dashboard ↗, go to Zero Trust > Integrations > Identity providers.
-
Find the JumpCloud integration and select Edit.
-
Turn on Enable SCIM.
-
(Optional) Configure the following settings:
- Enable user deprovisioning: Revoke a user's active session when they are removed from the SCIM application in JumpCloud. This will invalidate all active Access sessions and prompt for reauthentication for any Cloudflare One Client session policies.
- Remove user seat on deprovision: Remove a user's seat from your Cloudflare One account when they are removed from the SCIM application in JumpCloud.
- SCIM identity update behavior: Choose what happens in Cloudflare One when the user's identity updates in JumpCloud.
- Automatic identity updates: Automatically update the User Registry identity when JumpCloud sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and Cloudflare One Client device profiles; Access will read the user's updated identity when they reauthenticate.
- Group membership change reauthentication: Revoke a user's active session when their group membership changes in JumpCloud. This will invalidate all active Access sessions and prompt for reauthentication for any Cloudflare One Client session policies. Access will read the user's updated group membership when they reauthenticate.
- No action: Update the user's identity the next time they reauthenticate to Access or the Cloudflare One Client.
-
Select Regenerate Secret. Copy the SCIM Endpoint and SCIM Secret. You will need to enter these values into JumpCloud.
-
Select Save.
The SCIM secret never expires, but you can manually regenerate the secret at any time.
2. Configure SCIM in JumpCloud
- In the JumpCloud Admin Portal ↗, go to SSO Applications.
- Select the Cloudflare application that was created when you Set up JumpCloud as a SAML provider.
- Select the SSO tab.
- To provision user groups, select Include group attribute and enter
groups. The group attribute name has to exactly matchgroupsor else it will be sent as a SAML attribute. - Select the Identity Management tab.
- Make sure that Enable management of User Groups and Group Membership in this application is turned on.
- Select Configure.
- In the Base URL field, enter the SCIM Endpoint obtained from Cloudflare One.
- In the Token Key field, enter the SCIM Secret obtained from Cloudflare One.
- Select Activate. You will receive a confirmation that the Identity Management integration has been successfully verified.
- Select Save.
To check if user identities were updated in Cloudflare One, view your SCIM provisioning logs.
Provisioning attributes
Provisioning attributes define the user and group properties that JumpCloud will synchronize with Cloudflare Access. By default, JumpCloud will send the following attributes during a SCIM update event:
| JumpCloud user attribute | Cloudflare Access attribute |
|---|---|
email |
email |
firstname |
givenName |
lastname |
surname |
| JumpCloud group attribute | Cloudflare Access attribute |
|---|---|
name |
groups |
Example API configuration
{
"config": {
"issuer_url": "jumpcloud",
"sso_target_url": "https://sso.myexample.jumpcloud.com/saml2/cloudflareaccess",
"attributes": ["email", "name", "username"],
"email_attribute_name": "",
"sign_request": false,
"idp_public_cert": "MIIDpDCCAoygAwIBAgIGAV2ka+55MA0GCSqGSIb3DQEBCwUAMIGSMQswCQYDVQQGEwJVUzETMBEG\nA1UEC.....GF/Q2/MHadws97cZg\nuTnQyuOqPuHbnN83d/2l1NSYKCbHt24o"
},
"type": "saml",
"name": "jumpcloud saml example"
}