IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice question 6 of 30

Universal Containers (UC) plans to use a SAML-based third-party IdP serving both of the Salesforce Partner Community and the corporate portal. UC partners will log in 65* to the corporate portal to access protected resources, including links to Salesforce resources. What would be the recommended way to configure the IdP so that seamless access can be achieved in this scenario?

Full set: 248 questions
Answer options
A: Set up the corporate portal as a Connected App in Salesforce and use the Web server OAuth flow.
B: Configure SP-initiated SSO that passes the SAML token upon Salesforce resource access request.
C: Set up the corporate portal as a Connected App in Salesforce and use the User Agent OAuth flow.
D: Configure IdP-initiated SSO that passes the SAML token upon Salesforce resource access request. Correct answer
Correct Answer:
D. Configure IdP-initiated SSO that passes the SAML token upon Salesforce resource access request.
Explanation

The user journey starts at the corporate portal, where the partner is already authenticated via the third-party Identity Provider (IdP). When the user clicks a link to access Salesforce, the session initiation comes from the portal/IdP environment, not from Salesforce. This process, where the IdP sends a SAML assertion to the Service Provider (Salesforce) without a preceding authentication request from the SP, is defined as IdP-initiated Single Sign-On (SSO). This configuration enables the seamless access required by Universal Containers, as the user's existing authentication session with the IdP is leveraged to grant access to Salesforce.

Why Incorrect

A. Set up the corporate portal as a Connected App in Salesforce and use the Web server OAuth flow. This is incorrect because OAuth is primarily for authorization (API access), not authentication. The question specifies a SAML-based SSO requirement, making an OAuth flow inappropriate for this specific scenario.
B. Configure SP-initiated SSO that passes the SAML token upon Salesforce resource access request. This is incorrect because the user flow does not begin at the Service Provider (Salesforce). The user is already in the corporate portal, making the IdP the logical starting point for SSO.
C. Set up the corporate portal as a Connected App in Salesforce and use the User Agent OAuth flow. This is incorrect for the same reason as option A. The scenario requires a SAML-based authentication flow, not an OAuth flow designed for client-side applications to obtain access tokens.

References

1. Salesforce Help Documentation

"SAML SSO Flows": "In the IdP-initiated flow

the user logs in to the IdP

and then navigates to the SP. For example

a user logs in to their organization’s portal and clicks a link to access Salesforce." This directly matches the scenario described in the question.

Source: Salesforce Help

Identity and Access Management

Single Sign-On

"SAML SSO Flows".

2. OASIS Security Services (SAML) V2.0 Technical Overview

Section 3.4

"SSO Web Browser Profiles": The document describes the flow for an "unsolicited response" from an IdP to an SP

which is the technical basis for IdP-initiated SSO. It states

"The Identity Provider can also initiate an SSO exchange by sending an unsolicited Response to the Service Provider."

Source: OASIS SAML V2.0 Technical Overview

Committee Draft 02

25 May 2005

Lines 715-716.

3. Salesforce Architects

"Salesforce Identity and Access Management Architecture" Guide: This guide details different identity flows. In discussions of SAML

it clearly distinguishes between SP-initiated flows (starting at Salesforce) and IdP-initiated flows (starting at a third-party application or portal)

recommending the latter for use cases like the one presented.

Source: Salesforce Architect Digital Home

"Salesforce Identity and Access Management Architecture" PDF

section on "Federated Single Sign-On".

Scroll to Top