You need to sign in to do that
Don't have an account?
Anthony Robles
Connect App vs. Integration User
Hi,
There is no clear and simple explanation of what a connected app can be used for - if I want to query Salesforce through the REST API (for any reasons, from any external point), why would I need a "Connected App"? What's the difference with creating a Salesforce "Integration" User with an "Integration" Profile that restricts exactly what you want/need for that specific integration?
Thanks for anyone's help.
Regards
Anthony
There is no clear and simple explanation of what a connected app can be used for - if I want to query Salesforce through the REST API (for any reasons, from any external point), why would I need a "Connected App"? What's the difference with creating a Salesforce "Integration" User with an "Integration" Profile that restricts exactly what you want/need for that specific integration?
Thanks for anyone's help.
Regards
Anthony
User with an Integration Profile is just another user who is meant to do only api integration support within your organization. Connected App can be authenticated and authorized for any users even for Admins but its good practice to Authenticate and Authorize your connected app (external app) for this Integration User to be at the safer side.
So in that case, is it correct to say that a Connected App does not need to use any Salesforce User to perform actions within the Salesforce Database?
And in that case, let's say that my Connected App edits a record - what would be displayed in the "Last Modified By" in that case?
Which implies that the connected app is basically authenticated to an user within your organization. Once authenticated and authorized using OAuth the connected app receives an Access token which it uses to read / upsert data inside salesforce which again implies that each Access Token given to you by Salesforce for that connected app is an encrypted session that refers to the actual user who originally authenticated / authorized that connected app.
So In that case, Tthe LastModifiedBy will show that name of the user which is used by the connected app to gain access into salesforce.
- Creating a Salesforce API only profile, and then creating an Integration user with this profile who is an API only user.
- Creating a connected app, with Oauth 2.0 and necessary parameters for web server flow. (Client ID and client secret)
How does the Integration user get connected/related to the connected App ?>> So creating a valid Integration user is a combination of Creating a Salesforce API only profile, and then creating an Integration user with this profile who is an API only user.
Connected App and integration user/profile are not required for each other, you can create Integration profile without creating a connected app.
>> Creating a connected app, with Oauth 2.0 and necessary parameters for web server flow. (Client ID and client secret)
- Client ID and Secret will be generated by Salesforce and later can be fetched from the connected app info page, you cannot set them. These parameters are required also for other flows like JWT token flow, etc
>> How does the Integration user get connected/related to the connected App ?
The integration user will be logging in according to the selected OAuth flow like any other user, see https://help.salesforce.com/articleView?id=remoteaccess_authenticate.htm&type=5
You can control on Connected App and Profile side who can actually login throughout the Connected App, what scope is set for the connected user, etc.