Add JumpCloud SAML SSO integration guide

[joeduffy]

Summary

This PR adds a complete SAML SSO integration guide for JumpCloud as an identity provider for Pulumi Cloud, addressing the request in issue #13869. It follows the same structure and style as the existing guides for Okta, OneLogin, Microsoft Entra ID, Google Workspace, and Auth0.

Changes

• New file: content/docs/administration/access-identity/saml/jumpcloud.md — A full guide covering:

  • Creating the JumpCloud SSO application (with note about the SSO Package requirement)
  • Configuring SAML settings (SP Entity ID, ACS URL, RelayState, NameID format, signature algorithm)
  • Assigning users via User Groups
  • Exporting the JumpCloud IdP metadata XML
  • Completing configuration in Pulumi Cloud
  • Signing in (both IdP-initiated and SP-initiated flows)
  • Optional SCIM provisioning with links to Pulumi's SCIM docs and JumpCloud's own article
  • Troubleshooting pointer

• Updated file: content/docs/administration/access-identity/saml/_index.md — Adds JumpCloud to the integration guides list, alphabetically between Google Workspace and Okta. Also fixes the Google Workspace link to include a trailing slash for consistency with all other links in the list.

Notes on screenshots

This guide does not include screenshots. The existing Auth0 guide similarly works without them. JumpCloud's admin interface is straightforward to navigate with the textual instructions provided, and omitting screenshots keeps the guide maintainable as the JumpCloud UI evolves.

Primary source

JumpCloud's own Integrate with Pulumi support article was used as the authoritative source for configuration values and workflow steps.

Closes #13869

---

🧠 This PR was created by workprenticebot on behalf of @joeduffy.

[claude]

Docs review for #18605

Thanks for adding this JumpCloud guide — the structure mirrors the Okta and OneLogin guides well, the saml-warning shortcode is wired up correctly, all internal links resolve (/docs/administration/access-identity/saml/, /docs/administration/access-identity/scim/, /docs/administration/access-identity/saml/troubleshooting/, /brand/#logos), frontmatter is complete, and the menu weight: 45 slots JumpCloud cleanly between Google Workspace (40) and Okta (50). A few style and consistency items to address before merge:

Style guide compliance

Per STYLE-GUIDE.md: use "select" instead of "click," "navigate" instead of "go to," and "sign in" instead of "log in." The existing SAML guides (Auth0, Entra, Okta, gsuite) already follow this — JumpCloud should match.

content/docs/administration/access-identity/saml/jumpcloud.md:26 — Log in → Sign in:

1. Sign in to the [JumpCloud Admin Portal](https://console.jumpcloud.com/).

content/docs/administration/access-identity/saml/jumpcloud.md:27 — Go to → Navigate to:

1. Navigate to **User Authentication** > **SSO Applications**.

content/docs/administration/access-identity/saml/jumpcloud.md:28 — Click → Select:

1. Select **+ Add New Application**.

content/docs/administration/access-identity/saml/jumpcloud.md:29 — click **Next** → select **Next**:

1. Search for **Pulumi** to use the pre-built connector, or select **Custom Application** if a pre-built connector is not available, then select **Next**.

content/docs/administration/access-identity/saml/jumpcloud.md:30 — click **Next** → select **Next**:

1. On the **Select Options** page, choose the applicable options and select **Next**.

content/docs/administration/access-identity/saml/jumpcloud.md:38 — Click → Select:

1. Select **Save Application**, then **Configure Application**.

content/docs/administration/access-identity/saml/jumpcloud.md:59:

When you are done, select **Save**.

content/docs/administration/access-identity/saml/jumpcloud.md:67:

1. Select **Save**.

content/docs/administration/access-identity/saml/jumpcloud.md:73 and 75 — click → select for Export Metadata in both spots.

content/docs/administration/access-identity/saml/jumpcloud.md:83–86 — the existing guides use Select consistently; click **Change requirements**, click **Next**, and Click **Apply changes** should all use "select" to match. Compare to auth0.md:55–58 and okta.md:104–107.

Placeholder consistency

jumpcloud.md:48–50 uses acmecorp in the SAML table (matches the saml-warning shortcode — good). But jumpcloud.md:109 switches to <orgName> for the SCIM base URL:

| Base URL | \`https://api.pulumi.com/scim/v2/<orgName>\` |

The saml-warning callout on line 44 tells the reader to replace acmecorp, so a reader hits a different placeholder convention mid-page. The existing OneLogin SCIM guide (content/docs/administration/access-identity/scim/onelogin.md:47) uses acmecorp throughout; consider matching:

| Base URL | \`https://api.pulumi.com/scim/v2/acmecorp\` |

Minor nits

• jumpcloud.md:32: "JumpCloud will use this to construct..." — prefer present tense: "JumpCloud uses this to construct..."
• jumpcloud.md:63: "Users must be assigned to the JumpCloud application before they can sign in with SSO." — passive voice. Consider: "Assign users to the JumpCloud application before they can sign in with SSO."
• _index.md:40: The trailing-slash fix on the gsuite link is a good catch.

Notes

• The other SAML sidebar entries carry multiple legacy aliases (e.g., /docs/reference/service/saml-<idp>/). Since jumpcloud.md is brand new and those older URLs never existed, the single alias here is correct — no action needed.
• I couldn't verify trailing newline from the diff alone; if your editor preserves it, you're set.

---

Overall a well-written addition. The primary ask is the style guide pass; everything else is minor.

Mention @claude if you'd like another review after changes.

[pulumi-bot]

Your site preview for commit d4c0887 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-18605-d4c08873.s3-website.us-west-2.amazonaws.com

[joeduffy]

@claude All feedback addressed in the latest commit:

• Replaced all instances of 'click' with 'select', 'go to' with 'navigate', and 'log in' with 'sign in' per the style guide
• Updated the SCIM Base URL placeholder from `` to `acmecorp` for placeholder consistency
• Changed 'JumpCloud will use this to construct' to 'JumpCloud uses this to construct' (present tense)
• Changed 'Users must be assigned to the JumpCloud application' to 'Assign users to the JumpCloud application' (active voice)

Please take another look when you get a chance.

[pulumi-bot]

Claude finished @joeduffy's task in 39s —— View job

---

Re-review: All feedback addressed ✅

I've verified the latest commit against every item from the previous review. Here's what I found:

Style guide fixes — confirmed

Location	Change	Status
Line 26	Log in → Sign in	✅
Line 27	Go to → Navigate to	✅
Lines 28–30, 38	Click/click → Select/select	✅
Line 59	click **Save** → select **Save**	✅
Lines 73, 75	click **Export Metadata** → select **Export Metadata**	✅
Lines 83–86	click **Change requirements**, click **Next**, Click **Apply changes** → select throughout	✅
Line 81	Log in to Pulumi Cloud → Sign in to Pulumi Cloud	✅

Other fixes — confirmed

Location	Change	Status
Line 32	will use → uses (present tense)	✅
Line 63	Users must be assigned → Assign users (active voice)	✅
Line 109	<orgName> → acmecorp (placeholder consistency)	✅

_index.md — confirmed

JumpCloud is correctly inserted between Google Workspace (line 40) and Okta (line 42), alphabetically. The gsuite/ link has a trailing slash. All links are consistent.

---

This looks great — ready to merge. 🎉
| Branch

[CamSoper]

Verified against JumpCloud's current admin UI and their "Integrate with Pulumi" support article (https://jumpcloud.com/support/integrate-with-pulumi). The correct nav path is Access > SSO Applications, not "User Authentication > SSO Applications". Updated both occurrences. Everything else checks out.