Match each Identity and Access Management (IAM) protocol to its primary architectural use case.
- SAML 2.0XML-based web single sign-on (SSO) federation across enterprise enterprise boundaries
- OAuth 2.0Token-based authorization framework for delegated third-party API access
- OpenID Connect (OIDC)Authentication identity layer built on top of OAuth 2.0 using JSON Web Tokens (JWTs)
- RADIUSCentralized AAA protocol for network infrastructure, 802.1X, and VPN access control
Answer
SAML 2.0 matches XML-based web SSO federation; OAuth 2.0 matches token-based authorization for API access; OpenID Connect matches the authentication identity layer built on OAuth 2.0; RADIUS matches centralized AAA network access control.
Each IAM protocol satisfies a specific architectural domain: SAML 2.0 facilitates XML web federation across organizations; OAuth 2.0 grants granular authorization tokens to APIs; OpenID Connect adds an authentication identity layer over OAuth 2.0 using JWTs; RADIUS delivers network-level AAA for VPNs and wireless infrastructure.
Step-by-Step Solution
Key Concept
IAM Protocol Architectural Selection
Estimated Time:45s