Question 360
A vendor wants refresh privileges and administrative API access for a small one-time lookup. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Choose narrowly scoped OAuth grants and enforce least-privilege access independently of the OAuth scope string. Verification: Test allowed resources, user permission sets, sensitive fields and scope restrictions. Boundary: OAuth scope alone does not override object-level and record-level Salesforce access controls” addresses the access-design responsibilities in a vendor wants refresh privileges and administrative API access for a small one-time lookup Test against test allowed resources, user permission sets, sensitive fields and scope restrictions; oAuth scope alone does not override object-level and record-level Salesforce access controls.
Incorrect Answers
“Action: Coordinate Salesforce IdP signing certificate rollover with service providers and preserve fallback verification. Verification: Check Spring 2026 org restrictions, ECA policy, callback allowlists and credential controls. 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 test allowed resources, user permission sets, sensitive fields and scope restrictions for a vendor wants refresh privileges and administrative API access for a small one-time lookup The controlling boundary is: OAuth scope alone does not override object-level and record-level Salesforce access controls.
“Action: Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration. Verification: Test allowed resources, user permission sets, sensitive fields and scope restrictions. Boundary: Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration” may apply to a related identity task, but it does not establish test allowed resources, user permission sets, sensitive fields and scope restrictions for a vendor wants refresh privileges and administrative API access for a small one-time lookup The controlling boundary is: OAuth scope alone does not override object-level and record-level Salesforce access controls.
“Action: Choose narrowly scoped OAuth grants and enforce least-privilege access independently of the OAuth scope string. Verification: Inspect registered redirect URI, actual callback, state value and rejection logs. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy” may apply to a related identity task, but it does not establish test allowed resources, user permission sets, sensitive fields and scope restrictions for a vendor wants refresh privileges and administrative API access for a small one-time lookup The controlling boundary is: OAuth scope alone does not override object-level and record-level Salesforce access controls.