Question 0390 — Salesforce as an Identity Provider
At fictional Laurelfield Transit 39B, the team managing OAuth token lifecycle reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Periodically test redirect URI matching and review changes to connected-app callback lists. This recurring control addresses the observed problem: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. The measurable check is: Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.
Incorrect Answers
Reapprove connected-app scope sets during each API integration feature expansion. Periodically test redirect URI matching and review changes to connected-app callback lists.
Validate selected flow type against client capabilities and security requirements before deploying integrations. Periodically test redirect URI matching and review changes to connected-app callback lists.
Reconcile registered apps, scopes and named owners to the enterprise application inventory. Periodically test redirect URI matching and review changes to connected-app callback lists.