Question 0400 — Salesforce as an Identity Provider
At fictional Seabrook Systems 40B, the team managing connected-app authorization reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Test token type/audience separation at resource servers and connected-app boundaries. This recurring control addresses the observed problem: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. The measurable check is: Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.
Incorrect Answers
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.
Scan build artifacts and redirect configurations for client credentials and token leakage. Test token type/audience separation at resource servers and connected-app boundaries.
Validate selected flow type against client capabilities and security requirements before deploying integrations. Test token type/audience separation at resource servers and connected-app boundaries.