Security & procurement

What is single sign-on?

An authentication method that lets users log in to many applications with one corporate identity, usually via SAML or OpenID Connect.

Also called: sso, saml sso, saml, sso/saml

Single sign-on lets employees use their company identity provider to access software, instead of separate passwords for each tool. SAML 2.0 is the most common enterprise protocol, and OpenID Connect is widely used too. The identity provider enforces password rules and multi-factor authentication centrally.

In event software, SSO applies to two groups. Internal users like planners and marketers sign in to the admin tool, and sometimes attendees of internal or customer events sign in to registration or the app with their existing identity.

When buying, check which protocols and identity providers are supported, whether SSO can be enforced for all admins, whether it's included in your pricing tier and whether SCIM provisioning is available.

Why it matters for event marketers: Security teams often require SSO for any tool that holds customer or employee data.

How it works

SSO works by letting the event platform trust a company's identity provider (IdP) to confirm who a user is. With SAML 2.0, an OASIS standard from 2005, the user goes to the event platform, is redirected to the IdP (such as Okta or Microsoft Entra ID), signs in there with the company password and multi-factor authentication, and is sent back with a signed assertion that the platform accepts. OpenID Connect, built on OAuth 2.0, does the same with a more modern, token-based flow.

Admins set it up by exchanging metadata (certificates, URLs and identifiers) between the platform and the IdP, then mapping attributes such as email, name and group. Once SSO is enforced, password logins are switched off for those users, so offboarding in the IdP immediately blocks access.

What to look for in software

Check which protocols are supported (SAML 2.0 is the enterprise baseline, with OpenID Connect a common alternative), which IdPs have documented setup guides, whether SSO can be enforced for all admin users and whether just-in-time provisioning creates accounts on first login.

Ask whether SSO is available for attendees as well as admins, which matters for internal events and customer portals, and whether it's included in your plan or sold as an add-on. Pairing SSO with SCIM handles both login and account lifecycle.

Examples

Grip's help center lists SAML 2.0, OpenID Connect and OAuth 2.0 for SSO. Swapcard supports SAML 2.0 SSO for attendee and exhibitor login on its branded app add-on. Livestorm sells SAML SSO as an add-on, and Zuddl's security page lists SSO via SAML.

This site's security check tool shows which listed vendors document SAML SSO and SCIM.

Software categories

Tools for single sign-on (4)

Filter these in the directory →

Related terms

Frequently asked questions

What is the difference between SAML and OpenID Connect?
Both let users sign in with a central identity provider. SAML 2.0 uses XML assertions and is the long-standing enterprise standard for web apps. OpenID Connect is built on OAuth 2.0, uses JSON tokens and is common in modern web and mobile apps. Many vendors support both.
Can attendees use SSO to register for events?
Yes, for some platforms. Internal events and customer portals often let attendees sign in with their corporate or customer identity, which pre-fills registration and restricts access. Check whether the platform supports attendee SSO separately from admin SSO, since they're often different features.
Why do security teams require SSO for event software?
SSO centralizes login security: password rules and multi-factor authentication are enforced by the identity provider, and access is removed instantly when someone leaves. That reduces the risk of unauthorized access to attendee and customer data stored in event tools.
Is SSO included in all software plans?
Often not. Many vendors include SSO only on enterprise tiers or sell it as an add-on. Include it in pricing comparisons early if your security team requires it.
What is the difference between SSO and SCIM?
SSO handles how users sign in. SCIM handles whether user accounts exist and what roles they have, by automatically creating, updating and removing accounts from the identity provider. Enterprises typically want both.

Sources

Browse the full glossary