Question 0440 — Salesforce as an Identity Provider
At fictional Lighthouse Nonprofit 44B, the team managing OAuth token lifecycle reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Rehearse My Domain issuer and metadata rollovers with every external service provider. This recurring control addresses the observed problem: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. The measurable check is: Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.
Incorrect Answers
Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews. Rehearse My Domain issuer and metadata rollovers with every external service provider.
Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. Rehearse My Domain issuer and metadata rollovers with every external service provider.
Test token type/audience separation at resource servers and connected-app boundaries. Rehearse My Domain issuer and metadata rollovers with every external service provider.