Question 420
A mobile OAuth client fails after deployment because its redirect URI omits an expected path segment. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Fix authorization-code redirect registration, state integrity and callback matching before widening trusted origins. Verification: Inspect registered redirect URI, actual callback, state value and rejection logs. Boundary: Loosening redirect URI restrictions to accept arbitrary targets creates token interception risk” addresses the access-design responsibilities in a mobile OAuth client fails after deployment because its redirect URI omits an expected path segment Test against inspect registered redirect URI, actual callback, state value and rejection logs; loosening redirect URI restrictions to accept arbitrary targets creates token interception risk.
Incorrect Answers
“Action: Fix authorization-code redirect registration, state integrity and callback matching before widening trusted origins. Verification: Test device/user codes, verification URI, polling interval, expiration and consent. Boundary: OAuth scope alone does not override object-level and record-level Salesforce access controls” may apply to a related identity task, but it does not establish inspect registered redirect URI, actual callback, state value and rejection logs for a mobile OAuth client fails after deployment because its redirect URI omits an expected path segment The controlling boundary is: Loosening redirect URI restrictions to accept arbitrary targets creates token interception risk.
“Action: Separate identity claims validation from API token handling and enforce correct issuer, audience and nonce checks. Verification: Inspect registered redirect URI, actual callback, state value and rejection logs. Boundary: Device authorization is not a shortcut for unattended server access or bypassing user approval” may apply to a related identity task, but it does not establish inspect registered redirect URI, actual callback, state value and rejection logs for a mobile OAuth client fails after deployment because its redirect URI omits an expected path segment The controlling boundary is: Loosening redirect URI restrictions to accept arbitrary targets creates token interception risk.
“Action: Consider a supported device authorization flow only for an appropriate constrained client with secure user verification. Verification: Compare service provider metadata, Salesforce app configuration, subject claims and signed assertion. Boundary: Loosening redirect URI restrictions to accept arbitrary targets creates token interception risk” may apply to a related identity task, but it does not establish inspect registered redirect URI, actual callback, state value and rejection logs for a mobile OAuth client fails after deployment because its redirect URI omits an expected path segment The controlling boundary is: Loosening redirect URI restrictions to accept arbitrary targets creates token interception risk.