We’re seeing in our records that some instances have different
clientKeys although the
baseUrl was always the same.
Reading through the docs I can see the following paragraph:
Identifying key for the Atlassian product instance that the app was installed into. This will never change for a given instance, and is unique across all Atlassian product tenants. This value should be used to key tenant details in your app. The one time the clientKey can change is when a backup taken from a different instance is restored onto the instance. Determining the contract between the instance and app in this situation is tracked by AC-1528 in the Connect backlog.
And in that Jira issue (AC-1528) it says that:
This is because the clientKey is generated from the OAuth consumer key, which is seeded from the instance baseUrl. If the baseUrl changes, already installed add-ons may stop working.
Which, by my understanding, does not apply to this particular issue since the
baseUrl did not change.
My question is, therefore, in what scenarios, for the same addon and baseUrl, would we get lifecycle webhooks containing different
clientKeys. Also, would it be possible to be notified somehow that clientKey A changed in clientKey B for a particular baseUrl-addon combination?