Match each Identity and Access Management (IAM) protocol or standard to its primary architectural function in an enterprise environment.
- SAML 2.0Enables XML-based federated web Single Sign-On (SSO) between an Identity Provider and a Service Provider.
- OAuth 2.0Issues access tokens to grant third-party applications scoped authorization to access API resources on behalf of a resource owner.
- SCIMAutomates identity provisioning and user account lifecycle updates across cloud platforms using RESTful APIs.
- KerberosProvides ticket-based mutual authentication for users and services within an internal domain environment using a Key Distribution Center.
Answer
SAML 2.0 matches XML-based web SSO federation; OAuth 2.0 matches token-based API authorization delegation; SCIM matches automated identity provisioning and account lifecycle management; Kerberos matches ticket-based internal domain authentication via a KDC.
Each IAM protocol serves a distinct architectural layer: SAML 2.0 manages XML web SSO federation; OAuth 2.0 provides token-based API authorization; SCIM automates identity profile provisioning across cloud apps; and Kerberos performs ticket-based domain authentication.
Step-by-Step Solution
Key Concept
Identity and Access Management Architecture Protocols