Skip to main content

Identity Providers - Centralized Authentication Services

About 2 min read

An Identity Provider (IdP) is a service responsible for centrally managing users' authentication information and proving to other services that "this user is who they claim to be." Examples include Okta and Microsoft Entra ID (formerly Azure AD) deployed by enterprises, as well as consumer-facing Google accounts and Apple IDs. Without an IdP, users would have to create and manage a separate account for each service, leading to password fatigue and increased security risks.

The Relationship Between IdP and SP

The IdP is the party that provides authentication, while the SP (Service Provider) is the party that receives it. When a user accesses an SP, the SP delegates authentication to the IdP, and the IdP returns the result of its identity verification (an assertion) to the SP. This mechanism enables single sign-on (SSO), in which a user can use multiple SPs by logging in to the IdP just once.

IdP and SP Authentication Flow
User
① Access
SP
Slack, Salesforce, etc.
② Delegate auth
IdP
Okta, Entra ID, etc.
③ IdP authenticates the user → ④ Returns the assertion (authentication result) to the SP → ⑤ SP grants access

Major IdP Services

IdPPrimary AudienceCharacteristics
OktaEnterpriseOver 7,000 app integrations. Zero-trust support
Microsoft Entra IDCompanies using Microsoft 365Integration with AD. Conditional access
Google WorkspaceSMBs to large enterprisesSeamless integration with Google services
Auth0 (Okta)Developers and startupsFlexible API. Highly customizable

The Role of the IdP in SAML and OIDC

There are two main protocols used for the IdP to convey authentication results to the SP: SAML and OpenID Connect (OIDC). SAML is an XML-based protocol, while OIDC is a JSON/JWT-based protocol built on top of OAuth 2.0. In both protocols, the IdP's role is "verifying the user's identity and issuing the authentication result," but the data format and communication method differ.

The IdP in SAML

Issues SAML assertions in XML format. Sent to the SP through the browser, for example with the HTTP POST binding. Highly compatible with existing enterprise systems.

The IdP in OIDC

Issues ID tokens in JWT format. In the authorization code flow, the SP receives it from the token endpoint. Highly compatible with mobile apps and SPAs.

The Risk of the IdP Becoming a Single Point of Failure

Centralizing authentication in an IdP contributes to greater convenience and security, but it carries the risk of a single point of failure (SPOF): if the IdP itself goes down, users can no longer log in to any of the connected services. In October 2023, Okta's support system was accessed without authorization, and affected customers received individual impact reports. Points of comparison when selecting an IdP include its availability SLA, incident response structure, and whether backup authentication methods are available. Our startup security checklist also explains key points for choosing an IdP.

Federation and Directory Services

Federation is a mechanism by which different organizations trust each other's authentication information. For example, allowing a user authenticated by a partner company's IdP to access your own SP falls into this category. Directory services (such as Active Directory and LDAP) are databases that store user information within an organization, and in some setups the IdP references this directory to perform authentication. IAM (Identity and Access Management) is a broader concept that includes not only authentication but also authorization (managing access permissions).

Common Misconceptions

There is a misconception that "deploying an IdP makes your security airtight," but an IdP merely centralizes the gateway to authentication. If the IdP account itself is not protected by multi-factor authentication (MFA), then a breach of it can also affect the connected services. Our article on OAuth permission risks covers precautions when integrating with an IdP.

How Onboarding and Offboarding Account Management Changes

When each service has its own individually created accounts, the work of issuing them at onboarding and deleting them at offboarding piles up as the number of services grows, and an account left behind by a departed employee due to a missed deletion becomes an entry point for unauthorized access. Centralizing authentication in an IdP lets accounts be issued and disabled in one place on the IdP side, so at offboarding, disabling the IdP account alone cuts off access to all connected services at once. For users this appears as the convenience of no longer logging in to each service separately, but for administrators the essential point is that the ledger of access rights is consolidated in one place, making missed deletions structurally less likely. With everything consolidated into IdP accounts, a corporate password policy also becomes easier to enforce.

Was this article helpful?

Related Terms