Cannot Create Trusted Application Communication for Cloned Instance
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Configuring a trusted communication application between JIRA and a cloned Confluence instance failed due to this error message, thrown by JIRA:
The Trusted Application with the specified applicationId: confluence:14749191 already exists
Cause
Each of the trusted application configurations requires a unique application ID. In this case, the original application ID (14749191) owned by the production instance is associated to the cloned instance, too. JIRA is unable to proceed due to this clash.
Resolution
Please follow the steps outlined in How to create a cloned Confluence instance with a new server ID and application ID to generate a new unique application ID.