CCSP · Question #264
You work for a government research facility. Your organization often shares data with other government research organizations. You would like to create a single sign-on experience across the…
The correct answer is B. Security Assertion Markup Language (SAML). To enable single sign-on (SSO) and securely exchange user authentication and authorization data across multiple independent organizations, Security Assertion Markup Language (SAML) is the most appropriate protocol.
Question
You work for a government research facility. Your organization often shares data with other government research organizations. You would like to create a single sign-on experience across the organizations, where users at each organization can sign in with the user ID/authentication issued by that organization, then access research data in all the other organizations. Instead of replicating the data stores of each organization at every other organization (which is one way of accomplishing this goal), you instead want every user to have access to each organization's specific storage resources. In order to pass the user IDs and authenticating credentials of each user among the organizations, what protocol/language/motif will you most likely utilize? Response:
Options
- ARepresentational State Transfer (REST)
- BSecurity Assertion Markup Language (SAML)
- CSimple Object Access Protocol (SOAP)
- DHypertext Markup Language (HTML)
How the community answered
(51 responses)- B94% (48)
- C4% (2)
- D2% (1)
Why each option
To enable single sign-on (SSO) and securely exchange user authentication and authorization data across multiple independent organizations, Security Assertion Markup Language (SAML) is the most appropriate protocol.
REST (Representational State Transfer) is an architectural style for networked applications, not a protocol specifically designed for federated identity and single sign-on.
SAML (Security Assertion Markup Language) is an XML-based standard for exchanging authentication and authorization data between an identity provider and a service provider. It is widely used to enable single sign-on (SSO) across different security domains, allowing users to authenticate once and gain access to multiple services without re-entering credentials.
SOAP (Simple Object Access Protocol) is a messaging protocol for exchanging structured information in the implementation of web services, but SAML is specifically tailored for identity federation and SSO.
HTML (Hypertext Markup Language) is for structuring content on the web and plays no role in authenticating users or passing credentials between services for SSO.
Concept tested: Federated identity and single sign-on protocols (SAML)
Source: https://learn.microsoft.com/en-us/azure/active-directory/develop/single-sign-on-saml-protocol
Topics
Community Discussion
No community discussion yet for this question.