In confluence, how does switching from ajp to http impact applinks?

[Alexander Garcia]

Recently upgraded confluence from 6.15 to 7.3.2.  
We were having issues with synchrony so we switched our proxy connection from ajp to http... basically updated the proxy server for confluence to use the http module instead of the the ajp module. And we updated the server.xml file on the confluence server to remove the ajp connector

Everything in confluence appeared to be behaving normally but then we noticed the application links in JIra, Bamboo, and BitBucket can no longer connect to confluence.  Our proxy name and port hasn't changed so not sure why we are getting oauth errors:

2020-03-28 12:15:03,733 WARN [https-openssl-nio-8090-exec-8]
[oauth.serviceprovider.internal.AuthenticatorImpl]
logOAuthProblem Problem encountered authenticating OAuth client for url "https://confluence.grainger.com/rest/mywork/1/notification/metadata",
error was "signature_invalid",
with parameters "{oauth_problem=signature_invalid,
oauth_signature=####, oauth_signature_base_string=####,
oauth_signature_method=RSA-SHA1}"
-- url: /rest/mywork/1/notification/metadata | traceId: ####

We tried recreating the applink 

[Fabian Lim]

Hi Alex,

Take a look at this troubleshooting guide to assist you: https://confluence.atlassian.com/doc/troubleshooting-collaborative-editing-858772087.html

Regards