+44(0)1908 545 770
YOUR EXPERT RPA PARTNER

Team up with our RPA strategy and tech specialists for maximum automation impact

Find out more
Harness the power of UiPath in your business.
WATCH NOW

Save money and spend more time on priority work.

Book consultation
READY, SET, AUTOMATE

Let's choose, design and deploy a process automation solution for your business.

Find out more
TRANSFORM YOUR BUSINESS

Let's analyse your business to discover opportunities for innovation and automation.

Find out more

Begin your business transformation journey

Book consultation
AUTOMATE EVERY FUNCTION

Automate where it matters most. Scale to solve challenges in every area

Find out more
GIVE EVERY TEAM THE TOOLS FOR SUCCESS

Equip people with user-friendly solutions that save time and make work easier

Find out more

Which business problem
can we solve first?

Book consultation
10 August 2014

K2 Server Error – ID4223: The SamlSecurityToken is rejected

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.

Free K2 Five Upgrade Review

 

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:

K2 Appit SamlSecurityToken is rejected

K2 Appit SamlSecurityToken is rejected

Server Error
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'
More Details
Exception Details:
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
claimTypeMappings)
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.

Need further technical advice or support?