Configure a Custom Integration

Configure a custom integration when you want to protect a CDN, Load Balancer, Reverse Proxy or other components for which Bot Defense Standard does not have a preconfigured connector. When you configure a custom integration, you add a protected application in Bot Defense and copy a set of parameters that you need to complete the configuration process. You then complete configuration in the resource you want to integrate with Bot Defense.

Prerequisites

• You must have an active F5 Distributed Cloud account. If you do not have an account, see Create a Distributed Cloud Console Account.
• You must have Bot Defense enabled in the Distributed Cloud Console. See Enable Distributed Cloud Bot Defense Standard.
• You must have sufficient permissions in the application you want to protect to configure it with Bot Defense.

Configure a Custom Integration with Bot Defense

1. From the Distributed Cloud Console Home page, click Bot Defense.
2. Click Manage > Applications and then click Add Application.
3. On the Protected Application page, enter a Name and Description for the application.
4. From the Application Region drop-down menu, select the region where the origin server for the application resides.
5. From the Connector Type drop-down menu, select Custom.
6. Select Save and Exit.
7. On the Applications page, from the Actions column, click the Action menu (…) next to the protected application you just added.
8. From the drop-down list, click the following options and save the copied parameters in a location you can access later:
   • Copy App ID
   • Copy Tenant ID
   • Copy API Key
   • Copy Web API Hostname
   • Copy Mobile API Hostname
   • Copy Telemetry Header Prefix

Next Steps

When you finish adding the protected application to Bot Defense, use the parameters you copied from the Distributed Cloud Console to complete configuration in the CDN, Load Balancer, Reverse Proxy or other components you are integrating with Bot Defense.

When finished, test your integration. For information, see Test your Bot Defense configuration.