+ Start a Discussion

Connected app not using managed package

We would like to have several Salesforce accounts that individually authorize access via Oauth2. It would be preferred to deploy a connected app and have the same id and secret, but given that we would not be selling this app and making a profit we prefer not to go the managed package route.

Is the only alternative to this to create a seperate connected app for each Saleforce instance, and setup the integration using the unique ID and Client Secret?
You don't have to publish the package as managed to create a connected app keyset. I created one 2 years ago in a dev org and the keys are active.