Manual Chapter : Configuring advanced general settings on a profile

Applies To:

Show Versions Show Versions

BIG-IP FPS

  • 17.1.2, 17.1.1, 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.0
Manual Chapter

Configuring advanced general settings on a profile

Configure advanced general settings on
anti-fraud
profiles if you want to change the default settings that the BIG-IP system assigns to profiles.
  1. On the Main tab, click
    Security
    Fraud Protection Service
    Anti-Fraud Profiles
    .
    The Anti-Fraud Profiles screen opens.
  2. From the list of profiles, select the relevant profile.
    The Anti-Fraud Profile Properties screen opens.
  3. In the General Settings area of the Anti-Fraud Profile Properties screen, click
    Advanced
    .
    The Advanced settings appear.
  4. In the
    Alert Path
    field, use the automatically generated path, or define your own path.
    If you define your own path, ensure that the path is not used by any other field in the profile and that it is not an already existing URL.
  5. In the
    Alert Token Header
    field, use the default header or type a header that will be added to alerts that are generated on the client-side by JavaScript.
    This header secures communication between the client's browser and the BIG-IP system.
  6. In the
    Suggested Username Header
    field, use the default header or type a header that will be added to AJAX requests when the BIG-IP system detects an AJAX login attempt, which is common for Single Page Applications.
    With this header, the BIG-IP system can detect the username that was used for the login. The client sends this header only for URLs in the profile that have a parameter set as Identify as Username.
  7. For the
    JavaScript Directory
    field, use the automatically generated path, or define your own.
    This path specifies the location of the main
    FPS
    JavaScript. This path does not include the actual file name of the JavaScript.
    This path should be changed only if your application is already using a directory with the same path as the automatically assigned default path.
  8. For the
    JavaScript Configuration Directory
    field, use the automatically generated path, or define your own path that specifies the location of the
    FPS
    JavaScript containing profile configuration settings.
    This path specifies the location of the configuration JavaScript. This path does not include the actual file name of the JavaScript.
    This path should be changed only if your application is already using a directory with the same path as the automatically assigned default path.
  9. For the
    JavaScript Removal Location
    field, use the automatically generated path, or define your own path that specifies the location of the image file name that the system uses for detecting a JavaScript removal attack.
  10. For
    Threat Analytics Path
    , use the default path or define your own path for sending data to the Threat Analytics Platform (if enabled).
  11. For
    JavaScript Grace Threshold
    , change the default value if you want to raise or lower the maximum amount of time (in seconds) permitted between when a protected web page is loaded and its injected JavaScript activates.
  12. For the
    Collect Geolocation Coordinates
    setting, select the
    Enabled
    check box if you want the client to ask the end-user to grant permission to add geolocation coordinates to alerts.
  13. For the
    Collect Fingerprint Data
    setting, select the
    Enabled
    check box if you want the system to create a numerical fingerprint for identifying the client's computing device.
    This fingerprint is included in alerts sent to the FPS Dashboard.
  14. For the
    Fingerprint URL Location
    field, use the automatically generated path, or define your own path that specifies the location of the FPS JavaScript that calculates the fingerprint of the client's computing device.
    This path should be changed only if your application is already using a directory with the same path as the automatically assigned default path.
  15. Leave the
    Additional function to be run before JavaScript load
    field blank unless instructed otherwise by F5.
  16. If your profile includes one or more URLs that contain SPA views, for
    Referrer Info Header
    use the default header value or assign your own header value that the BIG-IP system uses to identify SPA views.
  17. For the
    Prevent duplicate alerts from Client Side
    setting, select the
    Enabled
    check box to prevent the client from sending an alert with information that is identical to an alert previously sent by the client during the past 24 hours.
  18. At the
    Ignore Predefined Alerts
    field, add the names of pre-defined alert definitions received from the F5 Update server that you want the system to ignore.
  19. For
    Maximum Length of HTML Attached to Test Alert
    , use the default length or type a number for the maximum length (in bytes) for the test alert.
  20. Click
    Save
    .
    The BIG-IP system saves the changes that you made to the advanced settings.