Hi SA. LifeTime expects a local time as internally it uses DateTime.Now for
compares. So, IIRC, the SCTNew returns a UTC string that is then converted
to local time before creating the LifeTime object and storing in the new SCT
on the client. Looking at the code again, it seems as that is what I did on
the client and server methods. Both client and server use local time in
LifeTime. But transfers the XMLSCT in a Zulu string to the client, which
the client converts before creating LifeTime. So you may have modified the
code in such a way as to pass a UTC time in the LifeTime constructor or
there is some funky date issue going on here (i.e. something I missed). I
hope it is the first case as that should be easy to fix. If the latter, you
may need to add some debug outputs on both side so we can see the UTC and
the local DateTimes on both sides that are being created/passed. Please let
me know. IMO, things like LifeTime should have been UTC based and IsCurrent
and IsExpired could just do the right thing. Cheers.

Signature
William Stacey, MVP
http://mvp.support.microsoft.com
> Hi all,
>
[quoted text clipped - 11 lines]
>
> MSFT: The docs should be more clear on this...