I have the same clock synchronization problem in my distributed application.
I am wondering if I need to put the time zone difference into consideration
when I set the timeToleranceInSeconds?
(My clients are in different time zone. They all access the web service in
the east coast.)
Also, I come across this scenario from the WSE 2.0 Service Pack 1 Readme
document under the Known Issues section. It said I could set the lifetime of
the issued token without sending in the creation time. By doing that, the
timing related errors would be avoided.
> Timestamp filter was gone. Timestamp header is a part of Security header, so
> it is handled by SecurityFilter.
[quoted text clipped - 157 lines]
> \\ blog: http://tim.mackey.ie //
> 67d0ebfec70e8db3
No different timezone does not require you to adjust any settings since WSE
Timestamps are stored in the UTC format s you shouldn't get any issues with
different timezones.
See WSE settings tool (Visual Studio). You can set the default TTL. But as
mentioned you can also increase the timeToleranceInSeconds to adjust for
machine time differences.
> I have the same clock synchronization problem in my distributed application.
> I am wondering if I need to put the time zone difference into consideration
[quoted text clipped - 54 lines]
> >
> > <securityTokenManager type="CustomUsernameTokenManager, WebForms"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
> > ty-secext-1.0.xsd"
> >
[quoted text clipped - 55 lines]
> >
> > <policies
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
> > y-utility-1.0.xsd">
> >
[quoted text clipped - 16 lines]
> >
> > <SecurityToken xmlns="http://schemas.xmlsoap.org/ws/2002/12/secext">
<wssp:TokenType>http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-user
> > name-token-profile-1.0#UsernameToken</wssp:TokenType>
> >
[quoted text clipped - 27 lines]
> > \\ blog: http://tim.mackey.ie //
> > 67d0ebfec70e8db3