An automation requires access to a Salesforce account that uses OAuth 2.0. You have already created a Connection in Integration Service. How should you access this connection within your UiPath Studio project?
Trap 1: Add the Salesforce username and password directly into the…
Hardcoding credentials directly into activity properties creates a significant security vulnerability and violates standard enterprise governance policies. Authentication should be handled through secure tokens or managed connections via Integration Service to prevent unauthorized exposure of production credentials within the source code of the automation project.
Trap 2: Use the 'Get Credential' activity to retrieve the OAuth token from…
While Orchestrator Assets are useful for storing basic credentials, they are not the intended mechanism for managing OAuth 2.0 flows in Integration Service. Manually managing tokens via assets adds unnecessary complexity and overhead to the workflow, whereas Integration Service handles token renewal and session management automatically.
Trap 3: Manually import the Salesforce private key into the project folder…
Importing private keys into the project folder poses a severe security risk and is considered a poor practice in UiPath development. Integration Service is designed to abstract these sensitive elements, providing a secure, centralized interface that eliminates the need to manage local keys or security certificates manually.
- A
Add the Salesforce username and password directly into the properties of the Salesforce application scope.
Why it fails: Hardcoding credentials directly into activity properties creates a significant security vulnerability and violates standard enterprise governance policies. Authentication should be handled through secure tokens or managed connections via Integration Service to prevent unauthorized exposure of production credentials within the source code of the automation project.
- B
Use the 'Get Credential' activity to retrieve the OAuth token from an Orchestrator Asset before every API call.
Why it fails: While Orchestrator Assets are useful for storing basic credentials, they are not the intended mechanism for managing OAuth 2.0 flows in Integration Service. Manually managing tokens via assets adds unnecessary complexity and overhead to the workflow, whereas Integration Service handles token renewal and session management automatically.
- C
Use the 'Use Salesforce Connection' activity to select the connection defined in Integration Service.
The 'Use Salesforce Connection' activity is specifically designed to consume existing connections established in Integration Service. This configuration allows the activity to leverage the OAuth 2.0 flow managed by the platform, ensuring that the automation remains authenticated without requiring manual credential entry within the Studio design environment.
- D
Manually import the Salesforce private key into the project folder to authenticate via the API.
Why it fails: Importing private keys into the project folder poses a severe security risk and is considered a poor practice in UiPath development. Integration Service is designed to abstract these sensitive elements, providing a secure, centralized interface that eliminates the need to manage local keys or security certificates manually.