IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice question 2 of 30

Universal Containers (UC) is planning to deploy a custom mobile app that will allow users to get e- signatures from its customers on their mobile…

Full set: 248 questions
Universal Containers (UC) is planning to deploy a custom mobile app that will allow users to get e- signatures from its customers on their mobile devices. The mobile app connects to Salesforce to upload the e-signature as a file attachment and uses OAuth protocol for both authentication and authorization. What is the most recommended and secure OAuth scope setting that an Architect should recommend?
Answer options
A: Id
B: Web
C: Api
D: Custom_permissions Correct answer
Correct Answer:
D. Custom_permissions
Explanation

The custompermissions scope is the most secure and recommended option as it adheres to the principle of least privilege. This scope allows a connected app to request access limited to specific functionalities that are gated by a custom permission within Salesforce. An administrator can create a custom permission (e.g., CanUploadESignature) and assign it only to authorized users. The mobile app then requests this specific scope, ensuring it only has the authorization to perform its designated task (uploading a file) and nothing more. This granular approach significantly reduces the attack surface compared to granting broad API access.

Why Incorrect

A. Id: This scope only provides access to the user's unique identifier and basic profile information; it does not grant permission to interact with or upload data.
B. Web: This scope is intended for web-based applications to access the user's session. It is overly permissive and not appropriate for a mobile app with a specific, limited function.
C. Api: This scope grants broad access to all of the user's data via APIs (excluding Chatter). It violates the principle of least privilege by providing far more access than the app requires.

References

1. Salesforce Help Documentation

OAuth Scopes: This document explicitly defines the purpose of each scope. For custompermissions

it states

"Allows access to the custom permissions in an org... This access allows a connected app to determine which custom permissions the user has on the fly." This highlights its use for fine-grained access control. (Salesforce Help

Document ID: help.salesforce.com/s/articleView?id=sf.remoteaccessoauthscopes.htm)

2. Salesforce Developer Documentation

Control Access to Your Connected App: This guide discusses security for connected apps. It explains that you can associate a custom permission with a connected app to limit access. The use of the custompermissions scope is the mechanism to enforce this limitation via the OAuth flow

aligning with security best practices. (Salesforce Developers

Connected Apps Section)

3. Salesforce Architect Decision Guides

Choosing a Salesforce Integration Security Mechanism: In discussions of integration security

the principle of least privilege is a core concept. The guide implicitly supports using the most restrictive scope necessary for an integration. The custompermissions scope is the most restrictive option available that meets the requirement. (Salesforce Architects

architect.salesforce.com/decision-guides/integration-security)

Scroll to Top