Troubleshooting: Multiple Tabs to the Same Realm Cause an Anti-Forgery Error

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: 19.07 and later
     
     

    Overview

    When a user opens multiple tabs to the same realm, one or both tabs can fail with an anti-forgery error, similar to:

    ASP.NET server error page showing HttpAntiForgeryException: The required anti-forgery cookie is not present, with the full exception stack trace.

     

    Cause

    Modern browsers don't isolate tabs from each other. Opening a second tab changes the anti-forgery value, but the first tab still expects the older value.

     

    Resolution:

    User education resolves this in most cases. If a workaround is needed that doesn't involve disabling anti-forgery protection entirely:

    1. In the Web Admin Console, go to the realm's Logs tab and enable Custom Errors.
    2. Change the Custom Error page to Restart.aspx.

    With this set, hitting the error restarts the session instead of failing outright, and redirects to SPStartURL if one is configured -- which can also spare the user a second login if they were already logged in from the other tab.


     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.