Question 0340 — Salesforce as an Identity Provider
At fictional Lighthouse Nonprofit 34B, the team managing OAuth token lifecycle reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Rotate integration credentials and review non-interactive principal scope during service ownership changes. This recurring control addresses the observed problem: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. The measurable check is: Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.
Incorrect Answers
Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
Periodically test redirect URI matching and review changes to connected-app callback lists. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
Reconcile registered apps, scopes and named owners to the enterprise application inventory. Rotate integration credentials and review non-interactive principal scope during service ownership changes.