Identity & Access Management

Single Sign-On (SSO)

Let users sign in once with their organization's identity provider, using SAML or OpenID Connect, with clean provisioning and session handling.

  • SAML and OpenID Connect

    Support for both major federation protocols, chosen per application and per customer.

  • SP- and IdP-initiated flows

    Sign-in that starts from your application or from the identity provider's app portal.

  • Just-in-time provisioning

    Accounts created automatically at first sign-in from the attributes the identity provider sends.

  • SCIM provisioning

    Automated creation, update and deactivation of accounts driven by the identity provider.

  • Multi-tenant SSO

    Per-customer SSO configuration for B2B products whose customers each bring their own identity provider.

  • Session and logout handling

    Consistent session lifetimes and logout behavior across the application and the identity provider.

What it is

Single sign-on (SSO) lets users sign in once with their organization’s identity provider (IdP), such as Microsoft Entra ID or Okta, and then access your application without a separate password. Your application, the service provider (SP), trusts signed assertions or tokens issued by the IdP instead of managing credentials itself.

Two protocols dominate. SAML exchanges signed XML assertions through the browser and is common in established enterprise software. OpenID Connect (OIDC) adds an identity layer to OAuth, using JSON Web Tokens, and fits modern web, mobile and API-based applications.

When you need it

  • Staff use many applications and password resets are a constant support burden.
  • Enterprise customers require SSO before they will buy your product.
  • You need access to end immediately when someone leaves.
  • Security policies require MFA, which is easiest to enforce centrally at the IdP.

How we approach it

We start by choosing the protocol per application: OIDC for new builds, SAML where a customer or existing system requires it. We then define the claims or attributes the application needs, such as a stable user identifier, email, name and group memberships, and how they map to application roles.

We support both flows. In an SP-initiated flow, the user starts at your application and is redirected to the IdP. In an IdP-initiated flow, the user clicks a tile in the IdP portal and arrives already authenticated. IdP-initiated SAML needs extra care, because the response is unsolicited, so we validate audience, destination and timing strictly.

For account creation, just-in-time provisioning creates a user at first sign-in, which is simple but does not handle leavers. SCIM lets the IdP create, update and deactivate accounts directly, which closes that gap. Many integrations use both.

Common pitfalls to avoid

  • Matching users by email. Emails change and can be reassigned. Link accounts on the IdP’s stable, unique identifier.
  • Skipping signature and audience checks. Every assertion or token must be validated fully, not just parsed.
  • Ignoring clock skew. Small time differences between servers cause intermittent failures unless a tolerance is set.
  • No plan for certificate rotation. IdP signing certificates expire. Reading metadata automatically avoids sudden outages.
  • Forgetting logout and deprovisioning. SSO that grants access but never removes it only solves half the problem.

Frequently asked questions

What is the difference between SAML and OpenID Connect?

SAML is an XML-based standard widely used by established enterprise applications. OpenID Connect is built on OAuth and uses JSON tokens, which suits modern web, mobile and API-based applications.

Do we still need passwords after adding SSO?

For users who sign in through SSO, no local password is needed. You may keep a separate, well-protected sign-in for emergency administrator access.

What happens when someone leaves the organization?

With SCIM, the identity provider deactivates the account in your application automatically. With just-in-time provisioning alone, you also need a way to detect and disable accounts that stop signing in.

Can each of our business customers use their own identity provider?

Yes. We build per-tenant SSO configuration so each customer can connect their own SAML or OIDC provider.

Let's build something great together

Ready to talk about custom software? Tell us about your project requirements and we will get back to you.