Your team just spun up another JetBrains Space project, and now everyone wants to log in with their single company account. The problem: passwords linger, tokens leak, and every new hire triggers a new round of permission chaos. This is where JetBrains Space SAML sweeps in to make identity management boring again—in the best way.
SAML, or Security Assertion Markup Language, lets organizations sync identity across systems. JetBrains Space supports SAML for Single Sign-On (SSO), which turns user management into a centralized, policy-controlled process. Instead of juggling credentials across tools, your company’s Identity Provider (IdP)—think Okta, Azure AD, or Google Workspace—authenticates once and hands Space a verified, signed ticket. The result: fast, auditable access without the sprawl.
To configure JetBrains Space SAML, start in your Space admin settings under “Authentication.” Create a new SAML connection and upload the IdP metadata (the XML blob your provider issues). Point it to your Space callback URL, verify your certificate fingerprint, and map attributes like username, email, and group. Space handles the rest, checking each login against your IdP’s assertion before granting access.
Most setups work smoothly, but a few points deserve special care. Ensure the system clock across your IdP and Space is in sync. SAML is picky about timestamps, and a few minutes of drift can break assertions. Map user groups carefully so Space mirrors your IdP’s roles. This avoids granting repo access to the wrong teams. Rotate certificates before they expire, not after, so you don’t lock everyone out mid-sprint.
Quick answer: To connect JetBrains Space with SAML, configure Space with your IdP metadata, verify the certificate fingerprint, and map user group attributes. Test with one account before going live to confirm your assertion and role mappings work as expected.