Redirect still applying after changing location

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • Version Affected: 9.x

    URL Rewrite is being used to detect a Users location and redirect them to a different realm.

    For example, one use case for this is to move Internal Users to a Windows SSO enabled realm to save them from typing their credentials when on premise. 

    The problem this KBA address is that this redirect continues to happen even after they've changed location. 


    Incorrect redirect type used on the URL Rewrite Rule. 


    When doing a redirect, URL Rewrite defaults to a 301 (Permanent)  redirect. This causes the Users browser to cache the redirect and not check in with IIS every time. 

    A better option is to use a 307 (Temporary) redirect. 

    1. Open IIS on the SecureAuth IdP
    2. Navigate to the URL Rewrite rule in question
    3. Edit the redirect type from a 301 to a 307 and Apply the changes

    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



    Please sign in to leave a comment.