Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
An identity provider (IdP) is a mechanism that takes on the identity check at login for everyone. Instead of each service checking passwords one by one, the IdP checks and passes only the result to the services. NIST's SP 800-63C-4 calls this idea federation.
How does an identity provider work?
Imagine a building's main reception. You finish the identity check at reception and receive a visitor pass. The rooms on each floor only check that the pass is genuine, and do not check who you are on their own. The reception is the IdP, and the rooms on each floor are the services you use.
NIST calls the service side the relying party (RP). The RP verifies the result of the identity check (the assertion) that arrives from the IdP, and then creates the logged-in state inside its own service. The RP trusts that the IdP hands over correct results.
The OpenID Connect specification calls a similar role the OpenID Provider. It is an OAuth 2.0 authorization server that can authenticate users. SAML is another federation method. The overall order of protecting logins is in unauthorized access countermeasures. For help choosing how to set one up, contact us.
Why does an identity provider matter?
NIST explains that federation means a user who uses several services does not need a separate authentication method for each. This advantage is known as single sign-on, a mechanism that lets you use several services with one login. It also brings account management together in one place.
The reverse side is dependence on the IdP. Because the RP acts by trusting the IdP, if the IdP stops, you cannot log in to the connected services. If an IdP account is taken over, the effect reaches the services beyond it. When you introduce or review one, check these points.
- Put multi-factor authentication on the IdP's administrator accounts.
- Decide the procedure for removing rights at the IdP when someone retires or moves.
- Prepare a separate administrator entrance for when the IdP stops.
- Keep a list of the connected services and the range of information handed over.
Introducing an IdP is not the goal in itself. It is a means to reduce the entrances you must protect and to narrow the places you must watch.
Related terms
- Single sign-on: a mechanism that lets you use several services with one login
- SAML: a method of passing identity check results between an IdP and each service
- OpenID Connect: a mechanism that does the identity check for login on top of OAuth 2.0
- Multi-factor authentication: confirms identity by combining several checks
Frequently asked questions
Are an IdP and single sign-on the same thing?
No. NIST says that being able to use several services through federation is also called single sign-on. An IdP is the name of the party that does the identity checking, and single sign-on is the word for the convenience that results.
What happens if the IdP stops?
You may be unable to log in to services that depend on it. NIST says the RP acts by trusting the result the IdP issues. Before you introduce one, decide the entrance for administrators when it stops and the procedure for contacts.
Next step
For the order of steps that protect logins across the board, see unauthorized access countermeasures. The free URL check shows only what is visible from outside, and for choosing and running an IdP, contact us.
Frequently asked questions
Are an IdP and single sign-on the same thing?
No. NIST says that being able to use several services through federation is also called single sign-on. An IdP is the name of the party that does the identity checking, and single sign-on is the word for the convenience that results.
What happens if the IdP stops?
You may be unable to log in to services that depend on it. NIST says the RP acts by trusting the result the IdP issues. Before you introduce one, decide the entrance for administrators when it stops and the procedure for contacts.