Error 404 Object not found when clicking on Vibe folders from a GroupWise client.

  • 7009524
  • 20-Jun-2012
  • 20-Jun-2012

Environment

Novell GroupWise 2012
Novell GroupWise 8
Novell Vibe OnPrem 3

Situation

You have configured a Vibe integration within your GroupWise system and assigned it to user via Client Options. Users upon login to their mailboxes get Vibe folder displayed. After authenticating to their Vibe accounts, a Vibe folder structure is populated but if they click on any personal folder, there is the error 404 displayed instead of expected Vibe folder content.

Resolution

There is a part of the security configuration setting missed in the Administration documentation, a chapter:

37.3.4 Defaulting to Secure HTTP URLs in Vibe Links

since version 3.2. In the version 3.1 it is still there present. Due to missing configuration in the Vibe site, all Vibe folders that were populated into a GroupWise mailbox have HTTP URL link which then fails to retrieve data from the Vibe account due to a security restriction. You could see incorrect HTTP link when viewing properties of any of such failing Vibe folders.
 
Steps for a resolution:
 
  • Locate ssf.properties file (on Linux /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/classes/config directory.
  • Open the file by any editor and locate following lines:
adapter.web.protocol=context-http
servlet.web.protocol=context-http
rss.web.protocol=context-http
ical.web.protocol=context-http
ssfs.web.protocol=context-http
simpleurl.web.protocol=context-http
  • Copy them and paste into ssf-ext.properties file at the bottom. Change all "http" -> "https":
adapter.web.protocol=context-https
servlet.web.protocol=context-https
rss.web.protocol=context-https
ical.web.protocol=context-https
ssfs.web.protocol=context-https
simpleurl.web.protocol=context-https
 
Then save the file and restart the Vibe services.

Cause

The Vibe is configured with the forced SSL settings.

Additional Information

Bug 767845 - We miss security configuration detetails in admin documentation since 3.1.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.