ID4223 The SamlSecurityToken is rejected
I am in the process of building a K2 Appit application. The product is extremely easy to use and I managed to put together quite a complex K2 for SharePoint Appit workflow in a few hours.
K2 Automated Testing Software
rnBenchQA allows full test automation of K2, including fully automated K2 SmartForms and K2 Workflow testing. It promotes test driven development for K2 and ensures continued quality assurance for K2 solutions. Easily apply changes to test cases to accommodate changes to K2 apps and ensure all apps are regression tested to avoid defects and assure continuous quality.
I encountered a small issue that is worth mentioning and what the solution is. While editing the workflow, the following error kept on popping up:
ID4223: The SamlSecurityToken is rejected because the SamlAssertion.NotOnOrAfter condition is not satisfied. NotOnOrAfter: '8/11/2014 2:44:28 PM'
Current time: '8/11/2014 4:24:06 PM'
at System.IdentityModel.Tokens.SamlSecurityTokenHandler.ValidateToken(SecurityToken token)
at SourceCode.Security.Claims.ClaimsResolver.ValidateSaml11TokenXml(String tokenXml, List`1 issuers)
at SourceCode.Security.Claims.SecurityClaims.ResolveClaimsToUserFullyQualifiedName(ClaimsTokenType tokenType, String tokenXml, Object issuers, Object
at SourceCode.Hosting.Server.Runtime.HostSecurityManager.GetClaimsUserName(String tokenXml, ClaimsTokenType tokenType, ClaimsVersion claimsVersion)
at SourceCode.Hosting.Server.Runtime.HostSecurityManager.AuthenticateIIdentitySession(String sessionCookie, String tokenXml, ClaimsTokenType tokenType,
Boolean isPrimarySecurityEntity, String authReqSource, ClaimsVersion claimsVersion)
The solution to the problem is surprisingly easy: simply clear the browser cache (IE & Chrome: Ctrl+Shift+Delete), reload the page and the error disappears.