Headers in Groove Web Services
Groove Web Services define two custom SOAP headers that are used in the SOAP messages: the GrooveRequestHeader and the GrooveResponseHeader. The GrooveRequestHeader provides information that Groove uses to ensure that the request comes from an authorized source, and to identify the Groove user that provides the service.
The GrooveResponseHeader is set by Groove and allows the calling application to ensure that it is communicating with the Groove process.
The GrooveRequestHeader provides the GrooveRequestKey and the GrooveIdentityURL. Groove uses the GrooveRequestKey to ensure that the request comes from an authorized source.
The Groove application provides a response key in the GrooveResponseHeader when it returns the response SOAP message to an application making local requests. Your application should check that this key matches the LocalResponseKey in the registry to verify that the response came from Groove. The Groove Data Bridge does not return a response key to remote SOAP requests.
Groove uses the Groove IdentityURL in the GrooveRequestHeader to identify the Groove user that provides the data. You should specify the Groove IdentityURL in all Groove Web Services operations except for GrooveAccounts.Read.
See Also
Reference
Headers Used in Groove Web Services