Previous Topic

Next Topic

Book Contents

Book Index

Synchronizing Server Clocks

OLSA implements the Web Services Security Username Token Profile 1.0 described in the following document:

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf

This security specification recommends that any web service provider reject any request whose creation time is older than five minutes. Skillsoft Hosting ensures that OLSA synchronizes with an atomic clock. The customer must also synchronize their server application environment with an atomic clock to avoid any time out issues.

If the server application environment is not synchronized with the web service, the user would see the following exception:

System.Web.Services.Protocols.SoapException: WSDoAllReceiver: security processing failed; nested exception is:

org.apache.ws.security.WSSecurityException: An error was discovered processing the header. (WSSecurityEngine: Invalid timestamp The security semantics of message have expired) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient Message message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(StringmethodName, Object[] parameters)