Question 0280 — Accepting Third-Party Identity in Salesforce
At fictional Ember Coast Media 28B, the team managing partner SSO registration reports: Two social providers return the same mutable email value, and a portal's registration handler silently links both to one customer identity. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Retest provider subject persistence and identity-link authorization after social-login connector changes. This recurring control addresses the observed problem: Two social providers return the same mutable email value, and a portal's registration handler silently links both to one customer identity. The measurable check is: Complete separate provider tests showing distinct issuers remain separated unless an approved account-link step succeeds.
Incorrect Answers
Audit registration handler relationships and contact-account ownership after community configuration changes. Retest provider subject persistence and identity-link authorization after social-login connector changes.
Maintain proactive signing-key expiry monitoring and cross-party change ownership. Retest provider subject persistence and identity-link authorization after social-login connector changes.
Continuously test tampered registration inputs and review default external permission settings. Retest provider subject persistence and identity-link authorization after social-login connector changes.