Skip to content

How SSO and Multi-Factor Sign-In Fit Together

Last checked November 15, 2026

SSO doesn't replace two-factor sign-in. They work side by side. SSO decides how many times you sign in. Multi-factor sign-in decides how strong each sign-in is.

What multi-factor means

Multi-factor authentication, or MFA, is also known as two-factor authentication. A user gets access only after presenting two or more distinct types of evidence.1

Those types are called factors. Two common ones:

  • Something you know. Knowledge only you have, such as a password.1
  • Something you have. A physical object in your possession, such as a security token or a phone.1

A password plus a code from your phone is two factors. Two passwords are not, because both are the same type.

Why SSO makes this matter more

With SSO, one sign-in opens many apps. That's the convenience. It's also the risk.

Wikipedia says that when credentials are available to other people and misused, SSO increases the negative impact.2 The advice is to pair SSO with strong authentication, such as smart cards or one-time password tokens.2

Picture a night-class building again. One key opens every room. You'd want a second lock on the front door.

Where the second check happens

In a SAML set-up, the identity provider does the checking. The standard doesn't specify the method of authentication at the identity provider. It may use a username and password or some other form, including multi-factor authentication.3

That's why the second factor usually sits there, at the front door, rather than inside each app. If "identity provider" is a new term, there's a short lesson on who plays which role.

Where the second check sitsYou open a work appApp sends you to the identity providerYou give a passwordYou give a second factorApp lets you in
One extra check at the identity provider covers the apps behind it.

What the app receives is an assertion from the identity provider, not your phone code itself. The login walkthrough shows that trip.

What changes for staff

  • They sign in once with two factors, not once per app.
  • They still need their second factor each time the identity provider asks for it.
  • An app that isn't connected to SSO has its own sign-in, so it needs its own second check.

How often the identity provider asks again depends on how your admin has set it up. Ask them, or read your identity provider's help pages.

The trade-off to plan for

Putting the strong check in one place also puts the risk in one place. If the identity provider can't be reached, a loss of its availability can mean people are denied access to every system unified under the SSO.2

So plan for a bad day. Know who can fix a lost phone or a broken sign-in system, and how fast.

A short checklist

  1. Is a second factor switched on at the identity provider?
  2. Which apps sit outside SSO, and do they have their own second check?
  3. What happens when someone loses their phone?
  4. Who can get in if the identity provider is down?

SSO and MFA aren't rivals. SSO cuts the number of sign-ins. MFA makes the remaining ones harder to fake.

Cited material

  1. Multi-factor authentication, Wikipedia
  2. Single sign-on, Wikipedia
  3. SAML, Wikipedia