Skip to content

Identity Providers and Service Providers

Last checked November 15, 2026

Every SSO set-up has two sides. One side knows who you are. The other side has something you want to use. The first is the identity provider, and the second is the service provider.

Say you run a small design studio. Your staff use a shared calendar app and a cloud accounting app. Each of those apps is a service provider. The thing that checks your staff's passwords is the identity provider.

The identity provider (IdP)

The identity provider is the one that holds the user credentials.1 It's the side that checks you. It might ask for a username and password, or for something more.

The SAML standard doesn't say how the IdP must check you. It may use a username and password or another form of authentication.2 A directory service that lets people log in with a username and password is a typical source of the proof an identity provider hands out.2

A directory service is just a central list of people and their sign-in details.

The service provider (SP)

The service provider is the app you're trying to use. It doesn't want to keep its own password for every person. So it asks the identity provider.

In SAML's words, the service provider requests and obtains an authentication assertion from the identity provider.2 An assertion is a statement about you, such as "this person signed in a minute ago." The SAML page opens one up.

Then the SP makes the call. On the basis of that assertion, it can decide whether to perform the service for the person.2

A quick comparison

Side Plain job Example in a small studio
Identity provider Checks who the person is1 The central sign-in system
Service provider Decides whether to let them in, based on what the IdP says2 The calendar or accounting app
The two sides of SSOPerson opens the work appApp asks the identity providerIdentity provider checks the personApp gets a statement about themApp lets them in or not
The app asks, the identity provider answers.

Many to many

One IdP can serve many apps. The SAML source says one identity provider may provide assertions to many service providers.2

The reverse works as well. One service provider can rely on assertions from many independent identity providers.2 That's the whole reason SSO saves effort. SSO shares centralized authentication servers that other applications use for authentication.1 Your studio sets up its sign-in system once, then connects each app to it.

Two words you'll see in settings screens

  • Relying party. A party that uses attributes from the identity provider to make access-control decisions.2
  • Principal. The SAML word for the person signing in.2

You may also see "IdP" and "SP" in admin panels. Now you know they're the two sides above.

What trust means here

The SP trusts the IdP's word. The service provider trusts the user information from the identity provider to provide access to its services.1

The next page, an SSO login step by step, shows what the two sides actually say to each other.

Cited material

  1. Single sign-on, Wikipedia
  2. SAML, Wikipedia