Question 0270 — Accepting Third-Party Identity in Salesforce
At fictional Westhaven Insurance 27B, the team managing B2E federation integration reports: A delegated identity service says Salesforce accepted a login, but operations cannot determine whether failure happened at the IdP, Salesforce SSO or a login policy. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Review correlated authentication logs and retention coverage after SSO policy updates. This recurring control addresses the observed problem: A delegated identity service says Salesforce accepted a login, but operations cannot determine whether failure happened at the IdP, Salesforce SSO or a login policy. The measurable check is: Reconstruct a synthetic failed SSO attempt across IdP and Salesforce timestamps, reasons and user mapping without logging secrets.
Incorrect Answers
Reconcile approved partner federation identifiers with Salesforce users before partner launch. Review correlated authentication logs and retention coverage after SSO policy updates.
Run full SP-initiated login and destination validation after reverse-proxy or gateway changes. Review correlated authentication logs and retention coverage after SSO policy updates.
Retest provider subject persistence and identity-link authorization after social-login connector changes. Review correlated authentication logs and retention coverage after SSO policy updates.