This server will be upgraded at 3pm Sydney time on December 3rd (December 2nd, 8pm PST) and will be down for up to 30 minutes.

Remote Publishing Plugin

Name Remote Publishing Plugin
Vendor Comala Technology Solutions, Inc. (Website)
Authors  
Homepage http://confluence.atlassian.com/display/CONFEXT/Remote+Publishing+Plugin
Issue Tracking http://developer.atlassian.com/jira/browse/APRV
Categories Content Macros
Version 1.0-rc2
Availability Confluence v2.5 to v2.8
State Beta
License Commercial
Price part of the Approvals Workflow Plugin
Java API Docs n/a
Download Source n/a
Download JAR remotepublishing-1.0-rc2.jar

This plugin allows for pages to be published to different confluence instances using the Approvals Workflow Plugin

Installation

This plugin requires the Approvals Workflow Plugin

See Installing Plugins and Macros

Documentation

See the Remote Publishing Example and the {remotepublish-page} macro

Labels

comalatech comalatech Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jul 24

    Darryl Lee says:

    Hey will this work if the Confluence site you're trying to post to is using SSL?...

    Hey will this work if the Confluence site you're trying to post to is using SSL?  What if it's using a self-signed certificate vs. one signed by Verisign, etc.?

    Is there any way to point at a local CA?

    Thanks! 

    1. Jul 24

      Roberto Dominguez says:

      Darryl, I've tried with a self-signed certificate and it failed... Have not tes...

      Darryl,

      I've tried with a self-signed certificate and it failed... Have not tested with a trusted CA yet, so I am not sure if it is going to work.

      Do you have access to a server with a trusted CA? Testing is very simple, just try this from the source COnfluence Server:

      {workflowproperties:publishing|url=https://serverwithssl/rpc/xmlrpc|user=remote|password=abc123|space=TEST}
      {remotepublishingtest}
      

      If you get a success message you are all set. Note that the plugin has to be installed only in the source Confluence instance.

      1. Jul 25

        Darryl Lee says:

        Hi Roberto: I just got a "real" cert from Verisign and installed it on the targ...

        Hi Roberto:

        I just got a "real" cert from Verisign and installed it on the target Confluence instance.  I'm still getting this error:

        Could not connect to https://sandbox.palm.com/rpc/xmlrpc: com.comalatech.confluence.rpc.XmlRpcException: could not login as remotepublisher with the given password into https://sandbox.palm.com/rpc/xmlrpc

        I have confirmed that I can log via the GUI into https://sandbox.palm.com/ with the username and password that is specified.

        I believe we've paid for this the Approvals Workflow product, so I'm going to follow-up with a direct e-mail since I believe we're entitled to some support for this, right?  :-} 

        1. Jul 25

          Darryl Lee says:

          Hey wait -- it's good to try fixing things yourself, right?  So I l...

          Hey wait -- it's good to try fixing things yourself, right?  So I looked in the logfile on the source server, and found this error message near the comaltech methods:javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

          Googling that last bit of the error, I found: 

          http://blogs.sun.com/andreas/entry/no_more_unable_to_find

          So it looks like I need to install the certificate on my source server, and it looks like Andreas provides a tool to do this in that blog post.

          I'm leery of running this on our production server, so can you please try it?  It is supposed to work with self-signed certs as well.

          Thanks! 

          1. Aug 07

            Roberto Dominguez says:

            Here's the deal: You would have problem only if you are trying to connect to a...

            Here's the deal:

            • You would have problem only if you are trying to connect to a remote confluence server with a self-signed SSL Certificate
            • You need to add you certificate to the client server. To do that see Connecting to SSL services
              • Retrieve the certificate (i.e. using openssl s_client -connect <HOST>:443)
              • Save the certificate (i.e. certificate.pem)
              • load the certificate keytool -import -alias <HOSTNAME> -file certificate.pem -keystore %JRE_HOME%/lib/security/cacerts
              • Restart the server

            Key things to keep in mind:

            • Make sure the common name of the certificate is the host name (that got me a few hours stuck)
            • You can use the SSLPoke tool in Connecting to SSL services to make sure the certificate was loaded properly