Create a Redirect from any Realm to a new Realm

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Hybrid
  • Version Affected:  ALL

    Description:  

    In certain instances, there may be the need or want to redirect from an old SecureAuth Realm to a new one, possibly due to deprecating a realm.

     

    Cause:  

    Deprecating a realm for an updated realm.

     

    Resolution:  

    Using the Rewrite tool within IIS you can create an easy rule to do the redirect.

    Launch the IIS Admin and select the realm you want to redirect FROM, then in the middle pane, double click the URL Rewrite icon icon.PNG
    Once the URL Rewrite tool launches, on the far right pane, click 'Add Rule(s)' under the Actions menu. AddRule.PNG
    When the wizard launches, select 'Blank Rule' and click 'Ok' BlankRule.PNG

    Give the rule a descriptive name

    Under "Match URL"

    In "Requested URL", select 'Matches the Pattern' in the drop-down

    In "Using", select 'Regular Expressions' in the drop-down

    In "Pattern", enter the value:   (.*)

     

    Expand "Conditions"

    Leave the default 'Match All'

    Click 'Add'

    Rule1.PNG

    In the "Add Condition" dialog

    Type, {HTTP_HOST}

    Select 'Matches the Pattern

    Set the 'Pattern' as:   .*

    Click 'Ok'

    mceclip0.png

    Under the "Action" area

    Select 'Action Type' as 'Redirect' in the drop-down

    Set the 'Redirect URL' to the realm or even URL that you want users to be redirected to

    Uncheck the 'Append query string'

    Set the 'Redirect Type' to 'Permanent (301)

    Rule2.PNG

    Once completed, click 'Apply' in the "Actions" menu on the far right of the console.

     

    Test the rule to ensure it works properly.

    mceclip1.png

     

    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.