How to block specific devices from authenticating against IdP

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


    How to prevent specific device types from authenticating based on their User Agent string.



    For policy or technical reasons it may be necessary to block particular device types from connecting to and authenticating with IdP.



    It's possible to block access based on specific words in user agent strings using the IIS rewrite module.  To do so, follow these steps:

    1. Obtain the user agent string.  This can be done by browsing to the following URL with the type of device to be blocked:
    2. Open IIS Manager, click on the server name then URL Rewrite 1.png
    3. Click Add Rule | Request Blocking 2.png
    4. Now choose the drop down for "Block access based on:" and select User-agent-Header.
      Change the Using: drop down to Regular expressions
      Then in the "Pattern" field type a list of words you want to block with a pipe | character as a separator.                                                    3.png
    5. The words you type here should be something in the user agent string specific to only the devices that should be blocked. For example this is the user agent string for a phone which is a Motorola Moto G6:
    6. Mozilla/5.0 (Linux; Android 8.0.0; moto g(6) Build/OPSS27.82-87-8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Mobile Safari/537.36 OPR/49.2.2361.134358
    7. In the example above, the model name is in the user agent string so "moto g" is used as the keyword.
    8. Finally there is a choice of 4 different options for "How to block:" Choose whichever method as desired.
    9. Now when the blocked device tries to get to the IdP it will be blocked and the end user will see a message similar to the below:





    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.