Enable Debugging for Fingerprinting Realms

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth IdP Version affected7x and Above


    This article discusses how to enable debugging for SecureAuth realms utilizing the Device/Browser Fingerprinting client side control.

    Note:These steps will instruct you on how to modify the SecureAuth configuration files which can impact the operation of your appliance. Serious problems might occur if you modify those files incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the files before you modify them. Then, you can restore the original files should a problem occur. If you are unsure about executing the changes or encounter any problems while following the instructions, contact SecureAuth support at +1 949 777 6959 Option 2 for assistance.

    1. Enable Fingerprint debugging for the realm

    • Open the SecureAuth administrative interface
    • Select the realm on which you would like to enable fingerprinting
    • Navigate to the System Info tab
    • In the Links section click the "Click to edit Web Config file." hyperlink
    • In the Web Config Editor locate the entry <add key="DFPDebug" value="False" />
    • Change the entry <add key="DFPDebug" value="False" /> to <add key="DFPDebug" value="True" />
    • Click the Save button to confirm the change


    2. Display Fingerprinting debug output

    • Open a browser window and visit the realm you configured in step 1
    • In the address bar append the following to the URL "?Debug=fp"
    • Press Enter
    • When the web browsers reloads follow the workflow as usual
    • After the "SecureAuth is checking your browser for a user credential." screen you will be presented with the debug results

    Info: The standard level of debugging provided by the command "?Debug=fp" is normally adequate to diagnose a problem. However you can request extended debugging information by changing the command to "?Debug=fp2", if needed.

    The debug option is case-sensitive as such the debug command must always be capitalized (e.g. ?Debug=fp).

    0 out of 0 found this helpful



    Please sign in to leave a comment.