2

We have two SF orgs SF1 and SF2. In SF1, we create a connected app, uploaded a digital certificate, and have policy of 'Admin Authorized user'. We added the needed profile. The client is able to connect via JWT token to SF1. Connecting to SF2 with same client id yields the error 'Missing Consumer Key Parameter' The client is using the same private key to sign the token. Also, the user belongs to the same profile in SF2. We are able to connect with Username Password flow to SF2. Will the same connected app not work in a different environment?

Improve this question
1
  • Username/Password flow also involves the same connected app, you're identifying it via client id + client secret. JWT flow has been flagged as behaving in a somewhat unpredictable fashion, e.g. in scratch orgs
    – identigral
    Commented May 14, 2020 at 17:25

1 Answer 1

Reset to default
2

Connected Apps in general work in any org (e.g. see the Data Loader, SFDX, etc). However, JWT-based flows need a Connected App per org, as far as I can tell. See for example Authorize an Org Using the JWT-Based Flow.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .