This guide will walk you through the process of integrating JumpCloud with Timus using SAML 2.0 for secure Single Sign-On (SSO). Follow these steps to configure your JumpCloud application and complete the setup within Timus Manager.

1️⃣ Create a New JumpCloud Application

1. Sign in to your JumpCloud Admin Console
2. In the left menu, go to SSO Applications

1. 
2. Click + Add New Application
   • If it's your first SAML app, click Get Started instead
3. Search for and select SAML 2.0

1. Click Next, then:
   • Display Label: Enter a name
   • (Optional) Upload a custom logo
   • Click Save Application

2️⃣ Configure Basic SAML Settings

After saving, you will be directed to the app configuration screen.

✅ JumpCloud uses the Display Label to auto-generate the Identifier. Ensure your app name is unique to avoid conflicts across SDNs in Timus.

3️⃣ Add User Attributes

1. Go to the Attributes section
2. Click + Add Attribute
3. Add the following fields:

4️⃣ Assign Users or Groups

1. Navigate to the User Groups tab
2. Select the groups who should have access to this SAML application
3. Click Save

Only users assigned to this SAML app will be able to authenticate through it.

5️⃣ Configure the Integration in Timus Manager

1. Navigate to Settings → Integrations → SAML 2.0 → Manage
2. Click Create New and fill in:

1. (Optional) Enable Require Encrypted Assertions if you’ve configured encryption
2. Define Allowed Sites and enable Remote Access if needed
3. Click Save

⚠️ Important: Use a Unique Application Name

JumpCloud generates the Identifier based on the application's name. For example, naming your app timusnetworks results in: https://sso.jumpcloud.com/saml2/timusnetworks

❗ This value must be unique across all SDNs.

To avoid conflicts:

• Always choose a unique Display Label
• This ensures proper tenant isolation and prevents login issues

✅ Test the Integration

1. Go to JumpCloud User Console
2. Sign in as a test user assigned to the SAML app
3. Click on the SAML app you just created
4. You should be redirected to Timus and signed in without being prompted for credentials again

The first successful login creates the user in Timus. Future sign-ins can occur directly from the Timus Connect application.

Troubleshooting Tips

• Make sure the app name (and thus the Identifier) is unique
• Use Hex format when copying the X.509 certificate
• Ensure the SAML attributes firstname, lastname, and nameID (email) are included
• Verify that the user has been assigned to the SAML application in JumpCloud
• Wait a few minutes after assigning users—JumpCloud may take time to apply changes

Updated July 15, 2025 03:58