Search the documentation
Search the documentation...
SplitSecure documentation

On this page

Concept · 3 min read

How SAML2 works

How SplitSecure acts as a SAML 2.0 identity provider that signs in to an app only after your Guardian Team approves.

Updated

SplitSecure can sign you in to AWS, Okta, Cloudflare and other services through SAML 2.0, with no password at the service. Each sign-in happens only when your Guardian Team, the group of devices that together approve each proposal, approves it.

What SAML 2.0 is

Two parties and an assertion

SAML 2.0 (Security Assertion Markup Language) is an open standard for single sign-on (SSO). One party proves who the user is, and the other party trusts that proof.

Party Role
Identity provider (IdP) Confirms the user and issues a signed SAML assertion
Service provider (SP) The service the user signs in to. It trusts the IdP and checks the assertion

A SAML assertion is a short, signed statement: “this user may sign in now”. The service provider checks the signature against the IdP’s certificate, which it received once, during the setup.

How a sign-in works

  1. The user starts the sign-in, at the identity provider or at the service provider.
  2. The identity provider confirms the user.
  3. The identity provider signs an assertion and sends it to the service provider.
  4. The service provider checks the signature and opens the session.

SplitSecure as your identity provider

A vote for every sign-in

In SplitSecure, the identity provider is a resource in a threshold vault. A threshold vault is a vault backed by a Guardian Team. The identity provider’s signing key belongs to that vault, so the key signs nothing without the Guardian Team.

When you sign in to a service, the Web App creates a proposal under Requests. The members of the Guardian Team approve it on their devices, in the mobile app. When the approvals reach the , the signs the assertion. The Web App then shows Login, which sends the assertion to the service.

Creating the identity provider is a proposal too. No setting approves a proposal automatically.

Connected apps

A connected app is one service that trusts your identity provider: an AWS account, an Okta organization, a Cloudflare account. You create it from the identity provider’s page with New Connected App. The form’s button reads Create Account; it creates a proposal, and the connected app appears under Connected Apps when the Guardian Team approves it.

Each connected app holds what SplitSecure needs to reach the service, such as the service’s metadata file. The service, in turn, holds the identity provider’s entity ID, sign-in address and certificate. Both sides come from the Web App and the service’s console; each service provider guide lists the exact values.

Two ways to start a sign-in

  • From SplitSecure (IdP-initiated). You open Connected Apps and click Authenticate. Every service provider guide tests the setup this way.
  • From the service (SP-initiated). You open the service’s sign-in page. The service sends you to the Web App, which asks for the same vote.

Either way, the Guardian Team votes on each sign-in, and the browser that asked for the sign-in finishes it.

Security guarantees

The signing key is never exported

Each identity provider has one RSA-4096 signing key. The key cannot be exported. It is used only inside the enclave, after a vote passes.

Every use is a fresh vote

An approval covers one sign-in. The next sign-in, by the same person to the same service, is a new proposal and a new vote.

The result reaches one browser, once

The enclave seals the signed result to a key that only the requesting browser holds. The browser deletes that key after the first use, so the Login button works once, in that browser profile only.

Short-lived assertions

The enclave signs the assertion, and the assertion stays valid for a few minutes. A copied assertion is of no use after that window.

Where to go next

Create the identity provider first, then pick your service from the service provider guides.