> I still do not get the error though as it is "After" since the Issue time in > SAML token shows 20:08 and the conditions had the on or after condition set > as 20:06
No the "NotBefore" time in the Assertion is "20:06". The "NotOnOrAfter" time is "20:13:33". The local time of the server, according to the logging was "15:28:31". Assuming a 5 hour time difference, the token is expired by 15 minutes when it hits the server. Colm. On Mon, Oct 6, 2014 at 5:26 PM, jeffc <[email protected]> wrote: > That "*" was an issue from when I tried to use nabble's message HTML > formats > for bold to highlight the times in the pasted XML. But it did not work in > XML so I removed nabble ** formatting but must have missed a spot. > > I still do not get the error though as it is "After" since the Issue time > in > SAML token shows 20:08 and the conditions had the on or after condition set > as 20:06 > > I had the admins verify the time synchronization between our STS server and > the applications server on which the service resides and they are in sync. > So why are we seeing this error and what are the options to resolve? > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/SamlAssertionValidator-SAML-Token-condition-Not-On-Or-After-not-met-tp5749413p5749477.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
