Question 0290 — Accepting Third-Party Identity in Salesforce
At fictional Laurelfield Transit 29B, the team managing external identity provisioning reports: An OIDC identity provider changes its issuer URL during a tenant migration, but Salesforce Auth Provider configuration still trusts the retired issuer. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance. This recurring control addresses the observed problem: An OIDC identity provider changes its issuer URL during a tenant migration, but Salesforce Auth Provider configuration still trusts the retired issuer. The measurable check is: Inspect a fresh ID token issuer, audience and signature and confirm the prior issuer no longer authenticates new sessions.
Incorrect Answers
Run full SP-initiated login and destination validation after reverse-proxy or gateway changes. Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance.
Audit partner joiner-mover-leaver synchronization against the source directory. Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance.
Retest provider subject persistence and identity-link authorization after social-login connector changes. Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance.