SSO Authentication

Sparkup supports single sign-on (SSO) authentication via the SAML v2.0 protocol. Once configured, your users can access Sparkup without creating a separate account—their authentication is managed by your identity provider (IdP).

This feature is only available with a Sparkup Enterprise license.

Compatibility

Sparkup is compatible with any identity provider that supports SAML v2.0, including:

• Microsoft Entra ID (formerly Azure Active Directory)
• Okta
• Any other SAML v2.0 IdP (OneLogin, PingFederate, ADFS…)

Automatic Account Provisioning (JIT)

Sparkup supports Just-in-Time (JIT) provisioning: participant accounts are created automatically upon the first SSO login, with no prior action required on your part. As soon as a user successfully authenticates through your IdP, their Sparkup profile is generated from the attributes provided (email, first name, last name).

Organizer accounts — JIT provisioning does not apply to organizers. Only an administrator of your Sparkup account can create organizer accounts on your instance.

IdP recommendation — we generally recommend granting access to the Sparkup application to all of your users in your IdP. Fine-grained access control (restriction by email domain or allowlist of addresses) is managed directly in Sparkup, at the session level, by the organizer.

Implementation Process

Step 1 — Define the instance domain name

Confirm the URL of your Sparkup instance, in the form yourcompany.sparkup.events. If you would like to use your own domain (e.g., events.yourcompany.com), this is possible through DNS configuration.
Once confirmed, provide this URL to Sparkup.

Step 2 — Retrieve the Sparkup metadata file

An XML metadata file containing the information required for configuration on the IdP side (Entity ID, ACS URL, signing certificate) is available from the Admin portal or can be provided by the Sparkup team.

Step 3 — Configure the IdP and send the client metadata

Your IT team configures the Sparkup application in your identity provider by importing the XML file from Step 2, then sends the metadata file from your IdP to Sparkup (through the Admin portal or by email).

Sparkup must be able to retrieve the following attributes during authentication:

Make sure these attributes are correctly mapped in your SAML application configuration.

Step 4 — Final configuration on the Sparkup platform

The IdP metadata is imported and the SSO configuration is finalized on your instance—from the Admin portal by your administrator or by the Sparkup team.

Step 5 — Testing

A test session to properly validate that authentication works from end to end: login from your IdP, attribute transmission, access to the Sparkup session, and verification of profile information.

SAML SP Technical Parameters

These values are required by your IT team to configure the Sparkup application in your identity provider. They are also included in the XML metadata file provided at step 2.