Security

SSO Architecture Diagram (SAML & OIDC)

Map single sign-on between identity provider, service providers, and the user browser.

Free to start · Fully editable · Export GIF, MP4, PNG & SVG

What's in this template

7 connected components you can rename, recolor, and extend with AI.

User BrowserService Provider AppSAML / OIDC ExchangeSAML Assertion / ID TokenUser Directory (LDAP)Session CookieMulti-Factor Authentication

This diagram explains single sign-on architecture, where one set of credentials grants access to many applications. It shows the trust relationship between an identity provider and multiple service providers, with the user's browser relaying assertions or tokens. The building blocks include the IdP, the SAML or OIDC protocol exchange, the assertion or ID token, the user directory, and the downstream service providers that consume the authenticated session.

IT admins, identity engineers, and SaaS vendors use this SSO architecture diagram to design federated login, document SAML and OIDC integrations, and explain session flow to stakeholders. It is useful for enterprise onboarding, security reviews, and troubleshooting authentication issues across connected apps.

Great for

  • Enterprise SaaS onboarding
  • Identity integration docs
  • Security reviews
  • IT admin runbooks
  • Vendor integration guides

Make your own version with AI

Prefer to start from your own content? Describe it in one sentence and Infogiph generates a sso architecture diagram you can edit and animate. For example:

“SSO Architecture Diagram showing User Browser, Service Provider App, SAML / OIDC Exchange, SAML Assertion / ID Token, User Directory (LDAP) and Session Cookie”

Try it in the AI diagram generator, or read Flow chart examples, including a login flow.

How to customize this template

  1. Open it in the canvas with Use this template.
  2. Tag each component with its trust zone, for example Browser (internet), Gateway (edge) or Ledger (internal), so boundary crossings stand out.
  3. Name each token where it appears, such as authorization code, access token, refresh token or ID token, and note how long it lives.
  4. Add PKCE to OAuth flows for mobile and single-page apps, since those clients cannot keep a client secret.
  5. In the RBAC Permission Model Diagram, list the real permissions each role gets, such as read, write or delete. Keep admin rights in one clearly marked role.
  6. Export a PNG or SVG for docs and slides, or a GIF or MP4 to keep the animation.

Frequently asked questions

What is SSO architecture?+

Single sign-on lets a user authenticate once with an identity provider and access multiple applications without logging in again. The IdP issues assertions or tokens that service providers trust.

What is the difference between SAML and OIDC for SSO?+

SAML is an XML-based standard common in enterprise apps, while OIDC is a JSON and OAuth 2.0 based protocol popular for modern web and mobile apps. Both establish federated trust.

What are the components of an SSO system?+

An identity provider, one or more service providers, the user browser, a user directory, and the protocol exchange that passes a SAML assertion or OIDC ID token.

How does SSO improve security?+

It centralizes authentication, reduces password reuse, and lets organizations enforce MFA and policy in one place rather than across every individual app.

Related templates

View all Security →

Make it yours in seconds

Open the sso architecture diagram (saml & oidc) in the Infogiph canvas, then edit, animate, and export.

Use this template