Can I create Application Links to crowd on a different domain?

Question

While the question is directed presently at Confluence/Crowd, it would go to Jira, Bitbucket, Crucible as well.  I am able to initiate the app link from Crowd to Confluence but it is failing to complete with Confluence claiming it can't connect to the Crowd server.  The recent change is that we are testing the Confluence server with new, different domain, SSL certs, which will eventually be rolled out to all Atlassian servers.

For now I'm hoping to learn whether or not there is a hard rule that would prevent Application Linking in a cross-domain deployment despite SSO working fine and there are no warning errors in the log analyzer.

Bastian Stehmann · Answer

Hmm,

Hmm, are all applications up to date? If not, there might be an incompatibility between the application link versions. Although I don't think that it is the case here.

https://confluence.atlassian.com/applinks/application-links-version-matrix-779174762.html

Or maybe you can find something in the troubleshooting section here.

https://confluence.atlassian.com/applinks/troubleshoot-application-links-755338283.html

David Hartje · Answer

Thanks for the reply I appreciate it.  Turns out the App linking between Crowd and the other apps isn’t working in Prod either so the issue is probably not related to the cross-domain we are evaluating in Test.  All the App-to-App links are working fine behind Apache proxy, but none of them will App link to Crowd.  I’m not really sure what the value even is for the App-to-Crowd backend linking because SSO works fine for them all with Crowd and so far I’m not aware of any functionality that was lost when we migrated to Apache Proxy (with SSL).

Any thoughts on the need for App-Crowd linking or why only those are failing?

Bastian Stehmann · Answer

Hi @David Hartje ,

Welcome to the community.

Application Links can be created without problems for different domains.

Maybe the servers can not communicate with each other due to a firewall problem. Or if you just changed the SSL certificate, it might be the problem that this has to be added to the java keystore.