|
|
The packaged External Client App’s client id and client secret is not visible to user.
Existing Connected Apps continue to function and can be deployed to new orgs. This change does not affect editing, installation (through packaging or OAuth installation), or deletion of Connected Apps. For more information, see External Client Apps.
|
|
Field
|
Description
|
|---|---|
|
Fields marked with * are mandatory.
|
|
|
External Client App Name*
|
Enter a unique name for the External Client App. This name helps administrators identify the app in App Manager.
|
|
API Name*
|
Enter the API name used to reference the app programmatically. By default, the system derives this value from the app name by replacing spaces with underscores. Ensure that the API name is unique and uses
• only letters, numbers, and underscores
• starts with a letter
• does not include spaces
• does not end with an underscore
• does not contain consecutive underscores
|
|
Contact Email*
|
Enter an email address that Salesforce can use to contact you or your support team if needed. This email address is not shared with Salesforce admins who install the app.
|
|
Distribution State*
|
Select how the external client app is distributed.
• Choose Local to develop the app for use only in the current org.
• Choose Packaged to develop the app for packaging and distribution.
|
|
Field
|
Description
|
|---|---|
|
Fields marked with * are mandatory.
|
|
|
Enable OAuth
|
Select this checkbox to enable OAuth authentication for the external client app. OAuth must be enabled to allow secure, token-based access to Salesforce APIs.
|
|
Callback URL
|
Enter the URL as https://portal.ptc.com/flow/oauths/oauth/return that Salesforce redirects users to after successful authorization. This URL must match the callback URL configured in the client application.
|
|
OAuth Scopes
|
Select the following scopes from Available OAuth Scopes and move them to Selected OAuth Scopes.
• Access the Salesforce API Platform (sfap_ap¡)
• Access the identity URL service (id. profile, email, address, phone) Full access (full)
• Full access (full)
• Manage user data via APIs (api)
• Perform requests at any time (refresh_token, offline_access)
|
|
|
To configure more fields, see Enable an OAuth Plugin.
|