Question 0320 — Salesforce as an Identity Provider
At fictional Pinehaven Commerce 32B, the team managing API integration authentication reports: An external partner portal must accept Salesforce employee identities via SAML, but the architecture team plans to make the partner authenticate against an untrusted copy of passwords. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. This recurring control addresses the observed problem: An external partner portal must accept Salesforce employee identities via SAML, but the architecture team plans to make the partner authenticate against an untrusted copy of passwords. The measurable check is: Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.
Incorrect Answers
Scan build artifacts and redirect configurations for client credentials and token leakage. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.
Periodically test redirect URI matching and review changes to connected-app callback lists. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.
Test token type/audience separation at resource servers and connected-app boundaries. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.