Question 0230 — Accepting Third-Party Identity in Salesforce
At fictional Asterline Education 23B, the team managing partner SSO registration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Include suspended and terminated users in JIT handler negative testing. This recurring control addresses the observed problem: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. The measurable check is: Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.
Incorrect Answers
Schedule certificate metadata audits and explicit rotation tests for each external identity provider. Include suspended and terminated users in JIT handler negative testing.
Test duplicate-address and provider-switch cases in every self-registration or social-login change. Include suspended and terminated users in JIT handler negative testing.
Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance. Include suspended and terminated users in JIT handler negative testing.