Question 0220 — Accepting Third-Party Identity in Salesforce
At fictional Pinehaven Commerce 22B, the team managing B2E federation integration reports: An external IdP rotates its SAML signing keys without coordinating Salesforce identity configuration, and some users can log in only through cached sessions. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Maintain proactive signing-key expiry monitoring and cross-party change ownership. This recurring control addresses the observed problem: An external IdP rotates its SAML signing keys without coordinating Salesforce identity configuration, and some users can log in only through cached sessions. The measurable check is: Compare certificate fingerprints, test a new assertion after rotation and confirm the retired signature is no longer accepted.
Incorrect Answers
Include suspended and terminated users in JIT handler negative testing. Maintain proactive signing-key expiry monitoring and cross-party change ownership.
Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance. Maintain proactive signing-key expiry monitoring and cross-party change ownership.
Check sandbox/production metadata independently after My Domain and domain-management changes. Maintain proactive signing-key expiry monitoring and cross-party change ownership.