Issue Summary

Upgrading Confluence to 9.2.14 or 10.2.3 results in a network error on the Application links page for all existing application links and OAuth connections.

Steps to Reproduce

Test 1

• Deployed Confluence version 9.2.13 alongside Jira 10.x.x.
• Established an Application Link between the two instances.
• Upgraded Confluence from version 9.2.13 to 9.2.14, during which network errors were observed in the logs.

  2026-02-06 12:22:54,637 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
  2026-02-06 12:23:04,094 WARN [Caesium-1-4] [atlassian.applinks.core.DefaultApplinkStatusService] logApplinkError Network error while attempting to retrieve status of Application Link '495a2c14-851f-3d29-9b12-0a9d8cd364a3' 

Test 2

• Deployed Confluence version 9.2.12 alongside Jira 10.x.x.
• Established an Application Link between the two instances.
• Upgraded Confluence from version 9.2.12 to 9.2.14, encountering network errors in the logs.

  2026-02-06 12:42:24,948 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
  2026-02-06 12:42:35,553 WARN [Caesium-1-4] [atlassian.applinks.core.DefaultApplinkStatusService] logApplinkError Network error while attempting to retrieve status of Application Link '495a2c14-851f-3d29-9b12-0a9d8cd364a3' 

Test 3

• Installed Confluence version 9.2.12 alongside Jira 10.x.x.
• Established an Application Link between the two instances.
• Upgraded Confluence from version 9.2.12 to 9.2.13; no network errors were observed in the logs during this upgrade.

  2026-02-06 12:54:57,896 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
  2026-02-06 12:55:07,797 WARN [http-nio-8090-exec-4 url: /confluence/rest/quickreload/latest/0] [impl.cache.hazelcast.ConfluenceHazelcastCacheManager] createDistributedCache Creating experimental asynchronous replicate-via-copy cache [com.atlassian.confluence.plugins.quickreload.QuickReloadCaches.lastUpdate]
   -- url: /confluence/rest/quickreload/latest/0 | referer: https://linux-117967.prod.atl-cd.net/confluence/admin/listapplicationlinks.action | traceId: c3e9fe0a3085e865 

Expected Results

Application links stay connected

Actual Results

The below exception is thrown in the atlassian-confluence.log file:

2026-02-06 12:42:24,948 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
2026-02-06 12:42:35,553 WARN [Caesium-1-4] [atlassian.applinks.core.DefaultApplinkStatusService] logApplinkError Network error while attempting to retrieve status of Application Link '495a2c14-851f-3d29-9b12-0a9d8cd364a3'  

Workaround (1)

Delete and recreate the application links. Applying this workaround will prevent an admin from bulk restoring AppLinks upon upgrading to a fixed version.

REST API options to delete existing application link

curl -X DELETE -u <username>:<password> -H "Accept: application/json" https://<Confluence_URL>/confluence/rest/applinks/1.0/applicationlink/<app_link_id>
curl -X DELETE -u <username>:<passowrd> -H "Accept: application/json" https://<jira_url>/jira/rest/applinks/1.0/applicationlink/<app_link_id> 

Note: Deleting or modifying an application link is a non-destructive process. Any existing macros or gadgets will resume functioning once the link has been recreated correctly. No content is removed as a result of removing an application link.

However, note that:

• Deleting then recreating an application link will force all of your users to log in again.
• If your instance has Project Links defined, these will be deleted along with the application link. They must be recreated after the application link has been recreated.

Workaround (2)

Fix broken application links by restoring the original host secret which was reset following upgrade to 9.2.14/10.2.3.

Note: If you have created any new application links since upgrading, this process will break these as this overwrites the newly generated host secret with the one used prior to upgrading to 9.2.14/10.2.3. This process will also not restore any broken application links you have deleted since upgrading.

For Confluence 9.2.14

1. Upgrade atlassian-oauth-consumer-sal-plugin to version 6.1.13
2. Shutdown Confluence and run the following SQL command:

   UPDATE PUBLIC.BANDANA t
   SET t.BANDANAVALUE = '<string>{ATL_SECURED}</string>'
   WHERE t.BANDANAKEY = 'com.atlassian.oauth.consumer.ConsumerService:host.__HOST_SERVICE__'; 

For Confluence 10.2.3

1. Upgrade atlassian-oauth-consumer-sal-plugin to version 7.0.8
2. Shutdown Confluence and run the following SQL command (please do not omit the newline character):

   UPDATE PUBLIC.PLUGIN_SETTING t
   SET t.SETTING_VALUE = '#java.lang.String
   {ATL_SECURED}'
   WHERE t.SETTING_KEY = 'com.atlassian.oauth.consumer.ConsumerService:host.__HOST_SERVICE__';