Question 0200 — Accepting Third-Party Identity in Salesforce
At fictional Seabrook Systems 20B, the team managing third-party IdP onboarding reports: An SP-initiated SAML flow loops between Salesforce and the corporate IdP because the AuthnRequest and RelayState are not preserved through a gateway. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Run full SP-initiated login and destination validation after reverse-proxy or gateway changes. This recurring control addresses the observed problem: An SP-initiated SAML flow loops between Salesforce and the corporate IdP because the AuthnRequest and RelayState are not preserved through a gateway. The measurable check is: Capture a full test handshake showing Salesforce request, IdP response, validated recipient and restored approved destination.
Incorrect Answers
Audit registration handler relationships and contact-account ownership after community configuration changes. Run full SP-initiated login and destination validation after reverse-proxy or gateway changes.
Include suspended and terminated users in JIT handler negative testing. Run full SP-initiated login and destination validation after reverse-proxy or gateway changes.
Audit partner joiner-mover-leaver synchronization against the source directory. Run full SP-initiated login and destination validation after reverse-proxy or gateway changes.