Hello @sumeet , yes, this is correct.
Connected App is describing the application that will be connecting, defining the scope of requested permissions, and other details. By itself, it has no other meaning.
When you use the connected app to connect to ANY org, the user needs to accept (or reject) this app with all the required permissions.
That means, you can create an app in any org, it does not really matter, it just has to exist, and connect to any Salesforce using this app as long as the user authorizes this connection and you receive the session tokens.
From the end-user org, you can create a workflow to limit connections for approved Connected Apps only, however, many don't have any restrictions and allow any app.
Connected App is describing the application that will be connecting, defining the scope of requested permissions, and other details. By itself, it has no other meaning.
When you use the connected app to connect to ANY org, the user needs to accept (or reject) this app with all the required permissions.
That means, you can create an app in any org, it does not really matter, it just has to exist, and connect to any Salesforce using this app as long as the user authorizes this connection and you receive the session tokens.
From the end-user org, you can create a workflow to limit connections for approved Connected Apps only, however, many don't have any restrictions and allow any app.
Statistics: Posted by MIvanov — Dec 02, 2023 9:39 pm
