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

Universal Containers (UC) has implemented SAML-based SSO solution for use with their multi-org Salesforce implementation, utilizing one of the the…

Full set: 248 questions
Universal Containers (UC) has implemented SAML-based SSO solution for use with their multi-org Salesforce implementation, utilizing one of the the orgs as the Identity Provider. One user is reporting that they can log in to the Identity Provider org but get a generic SAML error message when accessing the other orgs. Which two considerations should the architect review to troubleshoot the issue? Choose 2 answers
Answer options
A: The Federation ID must be a valid Salesforce Username
B: The Federation ID must is case sensitive Correct answer
C: The Federation ID must be in the form of an email address.
D: The Federation ID must be populated on the user record. Correct answer
Correct Answer:
B. The Federation ID must is case sensitive; D. The Federation ID must be populated on the user record.
Explanation

When a user successfully authenticates to a Salesforce Identity Provider (IdP) but fails to access a Service Provider (SP) org, the issue typically lies in the mapping of the user's identity between the two orgs. Salesforce uses the Federation ID in the SAML assertion from the IdP to identify the corresponding user in the SP. If the Federation ID is not populated on the user's record in the SP org, Salesforce cannot find a matching user and the login fails. Similarly, the Federation ID is case-sensitive. A mismatch in capitalization between the value sent by the IdP and the value stored on the user record in the SP will result in a failed match and a login error.

Why Incorrect

A. The Federation ID must be a valid Salesforce Username: This is incorrect. The Federation ID is a separate identifier used for SSO mapping and does not need to match the user's Salesforce username.
C. The Federation ID must be in the form of an email address: This is a common convention but not a technical requirement. The Federation ID can be any unique string value agreed upon by the IdP and SP.

References

1. Salesforce Help Documentation, "Troubleshoot SAML Login Errors": This official guide details common SAML errors. For the error "Subject... doesn't match any federation ID," the resolution explicitly states: "The Federation ID of the user in Salesforce is case-sensitive and must be an exact match to the Federation ID sent in the SAML assertion." This directly supports options B and D, as a missing or case-mismatched Federation ID will cause this failure. (Refer to the "SAML Assertion Errors" section).

2. Salesforce Identity and Access Management Architecture, "Single Sign-On" Chapter: This conceptual guide explains that for SAML-based SSO, the Service Provider (the destination org) uses an attribute from the SAML assertion to identify the user. When the "SAML Identity Type" is configured as "Federation ID," the system requires a populated User.FederationIdentifier field in the SP org that exactly matches the incoming value from the IdP. This confirms the necessity of the Federation ID being populated (D) and matching exactly (which includes case-sensitivity, B).

3. Salesforce Developer Documentation, "User" Object Fields: The field definition for FederationIdentifier on the User sObject specifies it as a case-sensitive string used for federated authentication. This confirms that the value must be an exact, case-sensitive match. (See the description for the FederationIdentifier field in the SOAP API Developer Guide).

Scroll to Top