SSO and identity
Choose between using your SpaceMedia platform as an identity provider or connecting an external one, and what each requires.
SpaceMedia supports single sign-on in both directions, and picking the wrong one wastes a configuration cycle.
| You want | Use | Meaning |
|---|---|---|
| Customers sign in to your other app with their platform account | SSO Identity | Your SpaceMedia platform is the identity provider |
| Customers sign in to your platform with an existing account elsewhere | SSO Consumer | An external provider is the identity provider |
| Signed-in customers reach your help desk without a second login | JWT SSO | Typically Zendesk |
Read that table before opening either section. The names differ by one word and the configurations are not interchangeable.
SSO Identity
Your platform issues the identity. Your own application becomes an OAuth client of it. Use this when you already have a product and want one account across both.
SSO Consumer
An external OAuth 2 provider issues the identity. You supply client credentials and the authorize, token, and user info endpoints. Use this when your customers already have accounts somewhere you control.
JWT SSO
Carries a signed-in customer into a connected help center without a second account. Useful when you run support outside the platform.
Before configuring
- These sections are locked until the trial starts. See Enterprise onboarding.
- Decide which direction you need. Changing later means reconfiguring both sides.
- Keep client secrets out of tickets, screenshots, and chat. See Privacy and safe support information.
- Test with a non-admin account, since an admin session can mask a misconfiguration.
Where the detail lives
Exact fields, endpoints, and callback formats for all three are documented at docs.spacemedia.uk.