Identity Training Kit - Exercise 3 - The SamlSecurityToken is rejected because the assertion's NotBefore condition is not satisfied.

Question

I'm following Exercise 3 on the Identity Training Kit. I get the following error after entering the "frankm" user and password. I'm not sure what causes this. Any help would  be appreciated. I succefully ran Exercise 1 and 2.

Environment:
Windows 7 Professional
IIS 7
Geneva Framework BETA 2

Error:

Server Error in '/ClaimsEnableWebSite' Application.
--------------------------------------------------------------------------------

ID4222: The SamlSecurityToken is rejected because the assertion's NotBefore condition is not satisfied.
NotBefore: 10/29/2009 7:17:25 PM
Current time: 10/29/2009 6:44:15 PM 
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: Microsoft.IdentityModel.Tokens.SecurityTokenNotYetValidException: ID4222: The SamlSecurityToken is rejected because the assertion's NotBefore condition is not satisfied.
NotBefore: 10/29/2009 7:17:25 PM
Current time: 10/29/2009 6:44:15 PM

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace: 


[SecurityTokenNotYetValidException: ID4222: The SamlSecurityToken is rejected because the assertion's NotBefore condition is not satisfied.
NotBefore: 10/29/2009 7:17:25 PM
Current time: 10/29/2009 6:44:15 PM]
   Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.ValidateConditions(SamlConditions conditions, Boolean enforceAudienceRestriction) +898
   Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.ValidateToken(SecurityToken token) +128
   Microsoft.IdentityModel.Tokens.SecurityTokenHandlerCollection.ValidateToken(SecurityToken token) +44
   Microsoft.IdentityModel.Web.TokenReceiver.AuthenticateToken(SecurityToken token, Boolean ensureBearerToken, String endpointUri) +79
   Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequest request) +177
   Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) +149
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.4927; ASP.NET Version:2.0.50727.4927 

Answer 1

Hm - i had that before - but in my case different machines were involved. Make sure your local time is synced. You can do that in the "clock applet" or "net time".

HTH

---

Dominick Baier | thinktecture | http://www.leastprivilege.com

Answer 2

Thanks for the tip -  didn't change anything, but it seems to work today. Perhaps some changes on the STS yesterday caused problems.