Using Groove Web Services Registry Keys

Applies to: SharePoint Workspace 2010 | Visual Studio 2008

It is possible for SharePoint Workspace to be shut down and then restarted while your SOAP client is executing. In this case, SharePoint Workspace assigns new values to the LocalRequestKey and LocalResponseKey keys. If it does not obtain the same port, it assigns new values to the GrooveHTTPPort and GrooveLocalHTTPPort keys as well. Consequently, your application should read these registry keys before calling each operation, and should not read them once and then re-use the values for multiple operations.

The request and response keys are stored in the HKEY_CURRENT_USER registry key and are encrypted using DPAPI CurrentUser encryption to ensure that Groove Web Services are only accessible to processes that are running under the same account. By providing the LocalRequestKey, your application demonstrates that it is running on the same Windows account as SharePoint Workspace.

See Also

Concepts

Reading Groove Web Services Registry Keys