Novell is now a part of Micro Focus

My Favorites


Please to see your favorites.

No Teaming folders synchronized in GroupWise client.

This document (7002238) is provided subject to the disclaimer at the end of this document.


Novell Teaming 2
Novell Vibe OnPrem 3
Novell GroupWise 8


Although all seems to be configured correctly on the Teaming and GroupWise site, in GroupWise client there are no teaming sub-folders displayed.
User can login in his Teaming account via web browser without problems.


To change the timeout value for web services authenticated through WS-Security, edit <tomcat>/webapps/ssf/WEB-INF/server-config.wsdd file in a text editor and make the following changes:

Locate the the following sections (there are two occurrences).

<handler type="">
<parameter name="passwordCallbackClass"
<parameter name="action" value="UsernameToken Timestamp"/>

Insert a "timeToLive" parameter with large timeout value (for example, 86400 for 24 hours). The resulting sections should look like the following.

<handler type="">
<parameter name="passwordCallbackClass"
<parameter name="action" value="UsernameToken Timestamp"/>
<parameter name="timeToLive" value="86400"/>

Save the file and restart the server.

Additional Information

Once you define client options using ConsoleOne, in the Teaming tab an URL link:
this one will be used saved in a GroupWise user database and will be used to access a Teaming server. GroupWise client does not have its own "Teaming functionality" but via specified URL makes a kind of SOAP / XML request to the Teaming server. When a user authenticates within a Teaming pop-up window, GroupWise client sends his credentials to a Teaming server. However, this SOAP request has also a time stamp information included with a time expiration / validity of 5 minutes. This can be seen from a trace taken between a client workstation and a Teaming server.
Thus when a teaming server has incorrect time or in general if there is more than 5 minutes time difference between a time that has a workstation where you run GroupWise client from and what is on the Teaming server, this login / sync request is ignored. Therefore if you see similar problems like that, make sure that a correct time is set on both, mainly on a Teaming server and also a client workstation running GroupWise client with a Teaming integration. Usually a problem with a time drifted is seen on a Teaming server.
When user access` his Teaming account via web browser, it is HTML protocol based request that does not have any time stamp information included in a request. That is why a web access usually works fine.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7002238
  • Creation Date:23-DEC-08
  • Modified Date:26-APR-12
    • NovellGroupWise

Did this document solve your problem? Provide Feedback