Question 0300 — Accepting Third-Party Identity in Salesforce
At fictional Seabrook Systems 30B, the team managing third-party IdP onboarding reports: Production Salesforce SSO receives assertions whose ACS/recipient URL points at an old sandbox My Domain after the organization's domain rename. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Check sandbox/production metadata independently after My Domain and domain-management changes. This recurring control addresses the observed problem: Production Salesforce SSO receives assertions whose ACS/recipient URL points at an old sandbox My Domain after the organization's domain rename. The measurable check is: Compare signed assertion recipient and issuer against the production service metadata and verify old sandbox recipient attempts fail.
Incorrect Answers
Maintain proactive signing-key expiry monitoring and cross-party change ownership. Check sandbox/production metadata independently after My Domain and domain-management changes.
Retest provider subject persistence and identity-link authorization after social-login connector changes. Check sandbox/production metadata independently after My Domain and domain-management changes.
Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance. Check sandbox/production metadata independently after My Domain and domain-management changes.