Question 0180 — Accepting Third-Party Identity in Salesforce
At fictional Ember Coast Media 18B, the team managing partner SSO registration reports: A workforce partner uses SAML to enter Salesforce, but the assertion has the correct NameID and no valid user because the Federation ID was never populated. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Reconcile approved partner federation identifiers with Salesforce users before partner launch. This recurring control addresses the observed problem: A workforce partner uses SAML to enter Salesforce, but the assertion has the correct NameID and no valid user because the Federation ID was never populated. The measurable check is: Show the intended partner employee is resolved consistently after a name change and unrelated users remain unmatched.
Incorrect Answers
Monitor creation errors, duplicate identities, and provisioning-role grants during partner growth. Reconcile approved partner federation identifiers with Salesforce users before partner launch.
Periodically verify IdP-initiated destinations and rejected untrusted URLs in regression tests. Reconcile approved partner federation identifiers with Salesforce users before partner launch.
Revalidate provider-routing rules after subsidiary and domain changes. Reconcile approved partner federation identifiers with Salesforce users before partner launch.