Symptoms
SmartForms users receiving the following error:
"ID4243: Could not create a SecurityToken. A token was not found in the token cache and no cookie was found in the context"
Error forces users to clear browser cache again and again to resolve this error.
Diagnoses
This is known issue (internal ID 544333) with K2 SmartForms security token handling which you may see in versions older than 4.6.11, for example 4.6.9. To resolve this issue you have to have K2 SF rollup SF 469.8 (fix is included in 4.6.11 release OOB) or newer and additionally made configuration changes described below.
Append Designer, Runtime and ViewFlow web.config files with the following settings:
1) <add key="Authentication.ClaimsErrorHandling" value="ID4243,true,~/;" />
in <appSettings>
2) <add name="ClaimsAuthenticationModule" type="SourceCode.Security.Claims.Web.ClaimsAuthenticationModule, SourceCode.Security.Claims.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16A2C5AAAA1B130D" />
in <system.webServer> <modules>
After making these changes restart K2 service and perform IIS reset.
With these settings in place it will not just refresh, but redirect to ~. In an ASP.NET application the framework controls recognize a tilde ('~') as a shortcut to the root of the application's virtual directory. You can read up on this here: Tilde (~) and Virtual Paths with ASP.NET
Resolution
Contact K2 support to obtain coldfix for versions older than 4.6.11 - refer to internal ID 544333 in your support request. Coldfix exists for 4.6.9. Install it and make configuration changes described above.
If you already run K2 4.6.9 with SmartForms rollup 469.8 or newer you only need to adjust configuration settings as described in Diagnosis section of this KB.
