How to run a secondary runtime site

  • 16 February 2021
  • 0 replies
  • 15 views

Badge +4
 

Known Issue: How to run a secondary runtime site

KB003693

PRODUCT
K2 Five
BASED ON
K2 Five

Issue

When a form is run via a normal runtime URL and the same form is run via a secondary runtime URL on the same browser, a JavaScript error occurs. This issue specifically arises when the secondary runtime site has a different identity (Application pool) and user compared to the original runtime site.

Error Code

Uncaught ReferenceError: __persistedFiltersDefinition is not defined

23239iFFA4BD7965F50E65.png

Since the original runtime and secondary runtime are run in the same browser this error is caused due to a cookie with identity data that is overriding the identity as set in IIS. This means that the resulting code path tries to run functions that would otherwise not be run for Anonymous sites.

Resolution

  1.  Comment out the following section in the secondary runtimes web.config file, which is located within the secondary runtime folder which you created.

    <!--<add name="WSFederationAuthenticationModule" type="System.IdentityModel.Services.WSFederationAuthenticationModule, System.IdentityModel.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="managedHandler" />--> <!--<add name="SessionAuthenticationModule" type="System.IdentityModel.Services.SessionAuthenticationModule, System.IdentityModel.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="managedHandler" />-->

  2. Run an IIS reset.
  3. Clear browser cache and refresh URLs for both runtime sites.
These config changes will mean that Federated authentication will not work on the Secondary Runtime site and the session authentication token cannot be restored with the Cookie on the Secondary Runtime site. These are not required for anonymous sites.

 


0 replies

Be the first to reply!

Reply