Hi Todd,

I am working with Atul on this problem.  We have our own application that is calling Clearspace web services using the client jars provided with Clearspace.  Specifically Jive built us a jar called jive-clearspace_community-webservices.jar, we are using that jar as well as its dependent jars.  We are trying to follow the examples given at

http://www.jivesoftware.com/builds/docs/clearspace/latest_2.0/ClearspaceWebServicesDevGuide.html#APIExamples.

Specifically our code looks something like this:

  ServiceLocator locator = new ServiceLocator(getCollaborationURL(), COLLABORATION_LOGIN, COLLABORATION_PASSWORD);
  UserService userService = locator.getUserService();

  WSUser clearspaceUser = userService.getUser(getClearspaceUserId());
  clearspaceUser.setEmail(getEmail());
  clearspaceUser.setName(getFullName());
  userService.updateUser(clearspaceUser);

getCollaborationURL() either returns https://ourserver/ or http://ourserver.  This works fine with http and we get the exception with https.

Thanks,

Aaron

Thanks for the suggestion, but the server is already configured to support HTTPS.  I can log in (as an admin or standard user) and use the site over HTTPS without problems.  It is only when connecting through webservice that we have a problem.

Hi Todd,

I am not sure I quite understand your response.  Are you suggesting that I need to upgrade to 2.5, or that I should be able to generate the necessary client jars for 2.0.3 myself using WSDL 2 Java? I am a little surprised that you were also not able to get the webservice to work over SSL, as the documentation suggests that it should work and that it is actually the recommended and default behavior.  I will attempt to build my own client jars and see how that goes, probably on Monday.  Can you provide any more concrete examples of this than the link above? I am new to WSDL2Java tools, so any time you can save me with more specific instruction would be valuable.

Thanks,

Aaron

Hi Todd,

I did a bunch of experiments and finally did get things working.  Building my own client jar did not work for me, as the client code generated did not match the signiture of the bundled client jar.  Switching over would have required me to rewrite a large amount of my own application code.

I went back to using the bundled client jar and started playing with my invocations.  The following code (simplified) was enough to get it working over SSL:

// webServiceURL looks like either "http://server/clearspace" or "https://server/clearspace"

ServiceLocator locator = new ServiceLocator(webServiceURL, login, password);

CommunityService service = locator.getCommunityService();

if (webServiceURL.toUpperCase().startsWith("HTTPS")) {
  Client cxfClient = ClientProxy.getClient(service);
  HTTPConduit http = (HTTPConduit)cxfClient.getConduit();
  TLSClientParameters tlsParams = new TLSClientParameters();
  tlsParams.setSecureSocketProtocol("SSL");
  http.setTlsClientParameters(tlsParams);
}

I still do not know why I had to do this, given the documentation indicated that it should work out of the box.  However, it all seems to be working just fine for me with this code.

-Aaron