Publish spaces to remote Confluence without Application Links
Description
Environment
Activity
David Majninger (K15t) October 11, 2021 at 2:42 PM
This feature request has been closed without resolution due to low interest and it being out of scope for the product in its current state.
We recommend trying out Scroll Documents, which is our new-generation and Cloud-compatible app for versioning and documentation management.
If you have any questions, please reach out to our support team.
Roman Serazhiev March 29, 2017 at 8:55 AM
Hi ,
I have tested the workaround and it works with OAuth (Impersonation) type of authentication set on both sides. I was able to publish a space to a remote Confluence after I have blocked all incoming connections on the source server and checked that it is not available from the outside.
Cheers,
Roman.
Roman Serazhiev March 9, 2017 at 9:06 AM
Hi ,
I haven't tested it in practice, but since Remote Publishing Endpoint (which is installed on a public-facing Confluence) never initiates any connections to Scroll Versions installed on a private Confluence, we are pretty sure the publishing should still work. When a user starts publishing, the network request is opened from Scroll Versions to Remote Endpoint. The later communicates back by responding within the same network request channel.
Have you tried one of the two other workarounds described here: https://jira.atlassian.com/browse/CONF-45418?
Cheers,
Roman.
Roy Lu March 8, 2017 at 6:58 PM
Thank you for creating this issue in your system. Looking forward to the new solution you guys will come up with! One quick question regarding the workaround, is it just a theory or you actually test it and confirm it is working?
Details
Details
Assignee
Reporter
Sync User [K15t]Components
Backbone Issue Sync
Backbone Issue Sync
Use-case scenario: I would like to publish from behind-the-firewall Confluence to a public facing one with Remote Publishing Endpoint. To achieve this, I have to connect Confluence instances with Application links. Even though Remote Publishing Endpoint doesn't create connections from target Confluence (public facing one) to a source once (behind the firewall), it is required to initially create the application link between two instances.
Since Confluence 5.10 it is no longer possible to create uni-directional links to other applications through Application Links. A potential solution would be to create our own mechanism of connecting to a target Confluence without the use of application links. That way we could create unidirectional links to workaround the lack thereof in Confluence 5.10 and above.
Workaround:
Allow incoming connections to behind-the-firewall Confluence
Set up application links
Disable incoming connections to behind-the-firewall Confluence
Remote publishing should now work