Configuring Redirect within IdP by User Agent

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth IdP Version Affected: All



    As an alternative to configuring redirects in IIS, you can also modify the Mobile Identifiers in an IdP realm for a specific user agent to redirect to another realm.


    Using a search engine, type in "my user agent" to generate the user agent of the operating system or device you are on:


    In the respective IdP realm, add the user agent as follows, ensuring a comma exists in-between each user agent:


    In this example, the change was configured on SecureAuth2. If a user accesses SecureAuth2 and has a user agent that exists within Mobile Identifiers, he or she will be redirected to SecureAuth3.

    Note that the release version of an operating system may be used for more than one operating system, so you will need to test across multiple operating systems prior to making the changes in a production environment.



    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



    Article is closed for comments.