HTTPS XnatPipelineLauncher

[TimOK]

We have an instance of XNAT 1.5.2 running over https. 

When the XnatPipelineLauncher is invoked with "-host https://..." we receive the following warning:

----------------

Jul 5, 2011 12:13:51 PM com.noelios.restlet.Engine createHelper

WARNING: No available client connector supports the required protocols: 'HTTPS' . Please add the JAR of a matching connector to your classpath.

net.sf.json.JSONException: Invalid JSON String

at net.sf.json.JSONSerializer.toJSON(JSONSerializer.java:143)

at net.sf.json.JSONSerializer.toJSON(JSONSerializer.java:103)

---------------

If we manually invoke XnatPipelineLauncher and modify the -host flag to use http, it works. Any suggestions? 

Haven't succeeded in finding the org.nrg.pipeline.manager package on bitbucket.

[Olsen, Tim]

Have you tried adding an aliasHost to XnatPipelineLauncher?

 

http://groups.google.com/group/xnat_discussion/browse_thread/thread/da6d8200cabbd745/45d8923aecf6e7c4?lnk=gst&q=aliasHost#45d8923aecf6e7c4

 

You can redirect your pipeline to http://localhost:8080 if it is always running on the same machine and doesn’t need to go over the network.

 

Tim

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/xnat_discussion/-/bq_1poyEKjAJ.
To post to this group, send email to xnat_di...@googlegroups.com.
To unsubscribe from this group, send email to xnat_discussi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/xnat_discussion?hl=en.

---

The material in this message is private and may contain Protected Healthcare Information (PHI). If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

[TimOK]

It turns out that the restlet client factory only needed to have access to a client connector that supports https. 

After adding the following three jars to the XnatPipelineLauncher classpath, https was supported:

org.apache.commons.codec.jar

org.apache.commons.httpclient.jar

com.noelios.restlet.ext.httpclient_3.1.jar

Only the last jar needed to be imported into XNAT from the restlet library. The remaining jars were present in the XNAT source.

[timok]