How To: Enable Fingerprint Debugging for a Realm

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: All

     

    Overview

    This article explains how to enable debugging for SecureAuth realms that use Device/Browser Fingerprinting (DFP) client-side control, and how to view the resulting debug output during login.

     

    Enable Fingerprint Debugging for the Realm

    1. Open the SecureAuth Admin Console and select the realm.
    2. Go to the System Info tab.
    3. Under Links, click Click to edit Web Config file.
    4. In the Web Config Editor, locate:

    <add key="DFPDebug" value="False" />

    1. Change it to:

    <add key="DFPDebug" value="True" />

    1. Click Save to confirm the change.

     

    View the Debug Output

    1. In a browser, go to the realm.
    2. Append ?Debug=fp to the URL and press Enter. The debug flag is case-sensitive -- it must be capitalized exactly as shown.
    3. Proceed through the login workflow as usual.
    4. After the "SecureAuth is checking your browser for a user credential" screen, the debug results are displayed.

    The standard ?Debug=fp output is normally enough to diagnose a problem. For extended debug information, use ?Debug=fp2 instead.


     

    Special Considerations

    Editing a realm's web.config file can affect how the appliance operates. Back up the file before making changes, so the original can be restored if a problem occurs. If you are unsure about making this change, or run into problems, contact SecureAuth Support before proceeding.


     

    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.