Configure an External Client App for OAuth 2.0 Client Credentials Flow
Use the OAuth 2.0 client credentials flow to share information between two applications
without any input from a user. In this flow, the client app exchanges its client credentials
defined in the external client app—its consumer key and consumer secret—for an access token. This
flow requires you to specify an integration user to run the integration.
Required Editions
User Permissions Needed
To view all external client apps, view their settings, and edit their OAuth policies
file
View all External Client Apps, view their settings, and edit their policies
Note Before you set up the client credentials flow, it’s important to understand its security
risks. With this flow enabled, any person or app that has access to your external client
app’s consumer key and consumer secret can get an access token. Maintain security by
periodically changing your consumer secret, and if it becomes compromised, change it
immediately. See Stage, Rotate, and Delete OAuth Credentials for an External Client App.
Open the ExtlClntAppGlobalOauthSettings file on your org.
Set the isClientCredentialsFlowEnabled field value to
true, and save the file.
Open the ExtlClntAppConfigurablePolicies file.
Set the isClientCredentialsFlowEnabled field value to
true.
Add the clientCredentialsFlowUser field, and enter the execution
user’s username.
Save the ExtlClntAppConfigurablePolicies file.
Deploy these changes.
sf project deploy start --manifest package.xml --target-org johndoe@example.com
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.