Integration between LinkedIn Sales Navigator and JumpCloud (SAML SSO)

Purpose

This implementation guide explains how to configure SAML-based Single Sign-On (SSO) between Sales Navigator and JumpCloud.

Prerequisites

• Valid JumpCloud admin access
• Sales Navigator admin access
• SAML metadata file exchange required between both portals

Step-by-Step Instructions

Step 1 — Configure SAML Authentication in Service Provider (Sales Navigator)

• Log in to Sales Navigator Admin Console
• Enable SAML Authentication
• Download the Service Provider Metadata (we will upload this into JumpCloud later)

NOTE: place your screenshot here of Sales Navigator SAML enable page

Step 2 — Configure Application in JumpCloud

• Sign in to console.jumpcloud.com
• Go to SSO → search/add Sales Navigator
• Set the Display Label (give any friendly name you prefer)
• Upload the metadata downloaded from Sales Navigator (from Step 1)
• Click Activate
• Download the JumpCloud Metadata file (we will upload this back into Sales Navigator)

NOTE: place your screenshot here of JumpCloud SSO App upload

Step 3 — Upload JumpCloud Metadata back to Sales Navigator

• Return to Sales Navigator Console
• Upload the JumpCloud metadata file
• Click Save

NOTE: place screenshot here of SP metadata upload page

Step 4 — Assign Users / User Groups in JumpCloud

• Go to SSO inside JumpCloud
• Open the Sales Navigator application
• Select Users and/or Groups who should have access
• Click Save

NOTE: place screenshot here of User/Group Assignment page

Expected Result / Validation

Users assigned to Sales Navigator in JumpCloud should now be able to login using their JumpCloud SSO authentication—redirecting via identity provider automatically.

FAQs

Q1: Does this work with both individual users and user groups?

Yes. You can assign individual users or JumpCloud user groups to the Sales Navigator SSO app.

Q2: Where do I find the SP Metadata file?

Inside Sales Navigator SSO configuration page where you enable SAML authentication.

Q3: Login failing even after configuration. What to check first?

Re-check if the SP EntityID and ACS URL in both metadata files match correctly.

Q4: Do I need to regenerate metadata if users change?

No. Metadata does not need re-generation for user addition/removal. Only when changing SAML endpoints.