An organization wants to utilize a common, Internet-based third-party provider for authorization and authentication. The provider uses a technology based on OAuth 2.0 to provide required services…

OpenID Connect (OIDC) is an authentication protocol that works on top of the OAuth 2.0 authorization framework, providing a standardized way for clients to verify the identity of the end-user based on the authentication performed by an authorization server. While OAuth 2.0 primarily handles authorization (granting access to resources), OIDC extends it to provide verifiable identity claims, making it suitable for both authentication and authorization through an internet-based third-party provider.

SAML (Security Assertion Markup Language) is an XML-based standard for exchanging authentication and authorization data between an identity provider and a service provider, but it is an independent protocol and not built upon OAuth 2.0.

XACML (eXtensible Access Control Markup Language) is a standard for expressing security policies and making access control decisions, focusing on fine-grained authorization policies rather than being an authentication protocol based on OAuth 2.0.

LDAP (Lightweight Directory Access Protocol) is an application protocol for accessing and maintaining distributed directory information services, used for querying and authenticating against directories, but it is not built upon or related to OAuth 2.0.