Release Notes : Guided Configuration 6.0

Applies To:

Show Versions Show Versions

BIG-IP APM

  • 16.0.0, 15.1.0, 15.0.1, 15.0.0, 14.1.2, 14.1.0

BIG-IP ASM

  • 16.0.0, 15.1.0, 15.0.1, 15.0.0, 14.1.2, 14.1.0
Release Notes

Summary:

Guided Configurations for BIG-IP Access Policy Manager and Advanced Web Application Firewall provide simple, workflow-driven configuration templates that cover common use case scenarios. Guided configurations can be easily created using the configuration templates. These configurations can be further edited, adding more components and apps, using the Guided Configuration interface.

Contents:

What are Guided Configurations?

Guided Configuration Overview

Guided Configurations for BIG-IP Access Policy Manager and Advanced Web Application Firewall provide simple, workflow-driven configuration templates that cover common use case scenarios. Guided configurations can be easily created using the configuration templates. These configurations can be further edited, adding more components and apps, using the Guided Configuration interface.

Guided Configurations are based on iAppLX technology, which is included with the Access Policy Manager and Advanced Web Application Firewall. Updates to Guided Configurations occur separately from BIG-IP upgrades, by installing use case packs, as detailed later.

Important: We recommend that you upgrade to the latest Guided Configuration use case pack when it is available. The latest use case pack will include additional templates, features, and fixes.
Note: The Guided Configuration is a bundle of configuration templates. Each configuration template in AGC has its minimal BIG-IP version. When upgrading AGC, the use case pack installation details the minimum BIG-IP version required for each configuration template. If the minimum requirement is not met, the template will neither be installed nor will they appear in the Guided Configuration. Click iApps > Package Management LX to see a list of installed packages.

Guided Configuration for Access Policy Manager

The Guided Configuration 6.0 release includes:

New enhancements to the Identity Aware Proxy configuration template for the Zero Trust use case. These include support for:

  • Unsigned client posture data
  • Allowing requests from domain managed devices
  • Additional contextual triggers - IP Address Change, User Group Check, HTTP Connector Request, and Device Posture Check
  • Adding multiple addresses in a virtual server
  • Selecting an existing HTTP Profile and Persistence Profile
  • Source session variable for a username and user group - AAA, OAuth, and SAML authentication
  • Selecting an existing Active Directory Trusted Domain
  • Multiple SSO methods
  • HTTP Headers with SSO
  • IP address in CIDR format
  • SSO NTLMV2
  • SSO OAuth Bearer for generating a JWT token or as a passthrough to use JWT from the client
  • Multiple trigger rules in the policy
  • Re-authenticating

To use the Logon Protection functionality in this template, you need to have a DataSafe license and FPS provisioned.

Note: To use the new features in Identity Aware Proxy, you need to have the BIG-IP system running 15.1.0 and provisioned for BIG-IP APM.

Configuration for the use case categories is available using Access > Guided Configuration. Configuration steps for authentication, endpoint posture checks, pools, and virtual servers are common to many of the configuration templates.

For a brief demonstration on creating a basic Identity Aware Proxy configuration, refer Identity Aware Proxy overview video.

Guided Configuration for Advanced Web Application Firewall

The Guided Configuration 6.0 release includes:

  • Enhancements to the Bot Protection and Web Application Comprehensive Protection configuration templates. The templates now allow you to provide verification and mitigation actions for OWASP Automated Threats based on a URL and hostname and configure whitelist objects to be exempt from mitigation.
Note: To use these features, you need to have the BIG-IP system running 15.1.0 and provisioned for BIG-IP ASM.

To use the IP Intelligence feature in the Web Application Comprehensive Protection template, you need to have the IP Intelligence license.

Configuration for the use case categories is available using Security > Guided Configuration. Configuration steps for pools and virtual servers are common to many of the configuration templates.

About Upgrading to Guided Configuration 6.0

Guided Configuration is upgraded with Use Case Packs provided on downloads.f5.com.

Upgrading the use case pack from the BIG-IP user interface

Download the use case pack from downloads.f5.com.
You can upgrade use case packs to get the latest guided configurations.
  1. On the Main tab, click Access > Guided Configuration or Security > Guided Configuration.
  2. On the top right of the page, click Upgrade Guided Configuration.
  3. Click Choose File and select the Use Case pack to upgrade.
  4. Click Upload and Install.

Upgrading the use case pack with the REST API

Download the use case pack from downloads.f5.com.
You can upgrade use case packs using a REST API.
  1. For purposes of this example, the use case pack is f5-iappslx-agc-usecase-pack-6.0-0.0.876.tar.gz. After downloading the use case pack, copy the pack to BIG-IP in location /var/config/rest/downloads/f5-iappslx-agc-usecase-pack-6.0-0.0.876.tar.gz. Make a POST request to install the use case pack, as detailed in the table.
    Item Description
    URI https://<bigip_address>/mgmt/tm/access/bundle-install-tasks
    METHOD POST
    Request Body {"filePath": "/var/config/rest/downloads/f5-iappslx-agc-usecase-pack-6.0-0.0.876.tar.gz"}
    Response Body
    {
       "filePath": 
        "/var/config/rest/downloads/f5-iappslx-agc-usecase-pack-6.0-0.0.876.tar.gz",
        "toBeInstalledAppRpmsIndex": -1,
        "id": "49c61e18-46e4-4501-bc2d-a4833e93833c",
        "status": "CREATED",
        "userReference": {
        "link": "https://localhost/mgmt/shared/authz/users/admin"
        },
        "identityReferences": [
        {
        "link": "https://localhost/mgmt/shared/authz/users/admin"
        }
        ],
        "ownerMachineId": "3f365fd8-81f8-4312-b837-f0080119635a",
        "generation": 1,
        "lastUpdateMicros": 1510767727481955,
        "kind": "tm:access:bundle-install-tasks:iappbundleinstalltaskstate",
        "selfLink": 
        "https://localhost/mgmt/tm/access/bundle-install-tasks/49c61e18-46e4-4501-bc2d-a4833e93833c”
    }
    
  2. Issue a GET command to check the use case pack installation, as detailed in the table. For purposes of this example, the use case pack is f5-iappslx-agc-usecase-pack-6.0-0.0.876.tar.gz.
    Item Description
    URI https://<bigip_address>/mgmt/tm/access/bundle-install-tasks
    METHOD GET
    Request Body {"filePath": "/var/config/rest/downloads/f5-iappslx-agc-usecase-pack-6.0-0.0.876.tar.gz"}
    Response Body (displays the installation status of each use-case RPM)
    {
       "filePath": "/var/config/rest/downloads/f5-iappslx-agc-usecase-pack-6.0-0.0.876.tar.gz",
       "frameworkRpmInfo": {
       "name": "f5-iappslx-access-framework-1.0.6.0-0.0.876.noarch.rpm",
       "status": "INSTALLED",
       "error": ""
       },
       "appRpmsInfo": [
       {
       "name": "f5-iappslx-access-oauth-auth-server-2.0.6.0-0.0.876.noarch.rpm",
       "status": "INSTALLED",
       "error": ""
        },
        {
        "name": "f5-iappslx-access-oauth-client-rs-2.0.0-0.0.876.noarch.rpm",
        "status": "INSTALLED",
        "error": ""
        },
        {
        "name": "f5-iappslx-access-saml-idp-1.1.0-0.0.876.noarch.rpm",
         "status": "INSTALLED",
         "error": ""
         },
         {
         "name": "f5-iappslx-access-saml-sp-1.0.0-0.0.876.noarch.rpm",
         "status": "INSTALLED",
         "error": ""
         }
         ],
         "toBeInstalledAppRpmsIndex": 4,
         "alreadyInstalledRpmsInfo": [],
         "step": "DONE",
         "manifestFileName": "pack-manifest.json",
         "manifest": {
         "description": "manifest of the AGC usecase pack",
         "usecasePackVersion": 2,
         "packages": [
         {
         "name": "f5-iappslx-access-framework",
         "version": "6.0.0",
         "minBigIpVersion": "14.1.0",
         "type": "framework"
         },
         {
         "name": "f5-iappslx-access-saml-idp",
         "version": "6.0.0",
         "minBigIpVersion": "14.1.0",
         "type": "usecase"
         },
         {
         "name": "f5-iappslx-access-oauth-auth-server",
         "version": "6.0.0",
         "minBigIpVersion": "14.1.0",
         "type": "usecase"
         },
         {
         "name": "f5-iappslx-access-oauth-client-rs",
         "version": "6.0.0",
         "minBigIpVersion": "14.1.0",
         "type": "usecase"
         }
         ]
         },
         "id": "49c61e18-46e4-4501-bc2d-a4833e93833c",
         "status": "FINISHED",
         "startTime": "2017-11-15T09:51:30.787-0800",
         "endTime": "2017-11-15T09:51:45.736-0800",
         "userReference": {
         "link": "https://localhost/mgmt/shared/authz/users/admin"
         },
         "identityReferences": [
         {
         "link": "https://localhost/mgmt/shared/authz/users/admin"
         }
         ],
         "ownerMachineId": "3f365fd8-81f8-4312-b837-f0080119635a",
         "generation": 17,
         "lastUpdateMicros": 1510768305736676,
         "kind": "tm:access:bundle-install-tasks:iappbundleinstalltaskstate",
         "selfLink": 
         "https://localhost/mgmt/tm/access/bundle-install-tasks/49c61e18-46e4-4501-bc2d-a4833e93833c"
    }
    

Known issues with Guided Configuration for BIG-IP Access Policy Manager

The following are known issues that affect Guided Configuration for BIG-IP Access Policy Manager.

ID number Description
671037 Guided Configuration does not currently conform to FIPS and Common Criteria requirements. Guided Configuration takes authentication server credentials (username and password) from the Secure Vault on the BIG-IP and stores them in an insecure ILX Restricted Storage, which does not conform with the secure storage requirements of FIPS, Common Criteria, PCI, HIPPA, or other modern security certifications, due to lack of protection for the master key.
672538-1 On a system configured with Access Guided Configuration objects, the command tmsh load sys config default, for loading the default config removes the BIG-IP configuration objects, but the AGC objects remain.

To remove the AGC objects, use the command clear-rest-storage. To keep the AGC objects, undeploy all AGC applications before you run tmsh load sys config default.

672791 When Guided Configuration is deployed in an HA environment, the Guided Configuration Use case configurations (iApps) are not synced to the peer device. When HA is configured in Manual Sync Mode, use case configurations are not synced to the HA peer. To ensure that HA is correctly configured for Guided Configuration iApps to function as desired, use a workaround. Configure the following settings for HA. As a workaround, configure your settings for HA as follows:
  • Open port 443 on any Self-IPs you are using for REST Config Sync.
  • When you set-up HA using the Run Config sync/HA utility from the BIG-IP UI, make sure you select Allow Default on the port lockdown setting of the Config Sync Self IP (internal or HA). The default setting is Allow Default.
  • Enable auto-sync on the failover device group.
  • Enable network failover on the failover device group.
676785 When Manage Configuration is disabled in Guided Configuration on a deployed configuration, the associated policy changes to Apply Policy status, and is highlighted in yellow. As a workaround, use the BIG-IP UI to apply the policy.
676902 When you upgrade the BIG-IP system to a newer build, and select Install Config as No, sometimes the contents of /var/config/rest/iapps from the old partition are not copied to the new partition. This results in a 404 error when you access Guided Configuration using Access > Guided Configuration .

As a workaround, use the command-line interface for Image upgrade:

  • When you want to move configuration from the old partition to the new partition, use the following TMSH commands: modify sys db liveinstall.moveconfig value enable modify sys db liveinstall.saveconfig value enable install sys software image BIGIP-tmos-bugs-staging-13.1.0.0.0.4796.iso create-volume volume HD1.2 reboot
  • When you do NOT want to move configuration from the old partition to the new partition, use the following TMSH commands: modify sys db liveinstall.moveconfig value disable install sys software image BIGIP-tmos-bugs-staging-13.1.0.0.0.4796.iso create-volume volume HD1.2 reboot
677964 When a user returns to Guided Configuration after navigating to other BIG-IP menus, the page fails to render in Internet Explorer, as it stops running JavaScript.
As a workaround:
  • Reload the page by refreshing the browser.
  • Close all Internet Explorer browser instances, restart the browser and navigate to Guided Configurations again.
681485 Only Common partition objects are supported. When objects from any other partition are selected, deployment fails. Only select objects from the Common partition when creating a configuration.
682360 In Guided Configurations, an iAppLX and an iApp can overwrite each other if they use the same app name. As a workaround, do not use the same name for a Guided Configuration iApp and an iApp (v1.0) instance. The same name cannot be used for two application configurations.
683765 Even if the configuration is locked, a user can modify customization settings outside of Guided Configurations. However, the customization settings from Guided Configurations can be restored simply by redeploying the configuration.
714573 When the device load is high, policy deployment might fail with a timeout error. As a workaround, wait until the device load is reduced, then deploy.
719634 Guided Configuration Synchronization in an HA environment has a particular set of configuration issues.
  • The administrator provides configuration properties using the Guided Configuration interface.
  • When the Guided Configuration is deployed, the iAppsLx framework deploys the configuration. A specific Guided Configuration processor deploys the configuration on the device.
  • The configuration is synced to peer HA devices regardless of HA mode (auto-sync or manual).
  • If HA mode is auto-sync when a deploy or undeploy action is taken, the configuration is deployed, and changes are synced to peer HA devices.
  • If HA mode is manual sync, you must manually sync these changes to other devices when a configuration is deployed or undeployed.

As a result of the configuration options, it is possible that the Guided Configuration application status (deployed, pending, or not-deployed) may not reflect the state of configuration objects when the sync mode is manual. It is recommended that the administrator should use auto-sync mode when devices are in an HA environment.

720432-1 When you undeploy a configuration created with Guided Configuration, the LTM Nodes are not deleted. As a workaround, delete the nodes manually from the BIG-IP UI, or with TMSH.
720703 In the OAuth Client & Resource Server Guided Configuration, if the administrator modifies the deployed configuration then attempts to redeploy, deployment may fail. As a workaround, either use the existing DNS resolver when configuring AGC or after modifying the configuration, undeploy, then deploy again.
739996 When you create an OAuth authorization server (AS) and a resource server (RS) together, and access RS as a client, using the Logon using Authorization Code grant type option, you are redirected to the AS logon page. This page sometimes repeatedly timeouts before opening an incorrect landing URI.
744288 The virtual servers displayed in Credential Protection AGC are the ones that had been created by Traffic Management User Interface (TMUI) with Access profiles. The virtual servers created and deployed with AGC are not available for adding to Credential Protection.

You cannot add Credential Protection to an existing AGC deployment. For example, you cannot create an AGC SAML IdP deployment, then use AGC Credential Protection and add it to the AGC SAML IdP deployment.

As a workaround, to create an AGC deployment with Credential Protection, follow these steps:

  1. Create the desired AGC deployment.
  2. Recreate manually the objects created by AGC deployment using TMSH or TMUI.
  3. Run the Credential Protection AGC and apply the credential protection to the app created in step 3.
750761 When you change the ADFS Pool Health Monitor value in a deployed configuration and redeploy, the new health monitor is set up on the pool, but the UI shows the old monitor value.

As a workaround, to display the new monitor assignment in UI, follow the steps below:

  1. Assign the old_monitor value to the pool and deploy the config.
  2. Un-deploy the configuration to remove the old_monitor association to the pool.
  3. Assign the new_monitor value to the pool and deploy the configuration.
752556 When you deploy the API Protection Proxy configuration and then disable the Managed Configuration feature, the Apply Access Policy link is shown in the top left of the AGC screen. You cannot apply the policy using this link, as this link opens an empty page instead of displaying the list of access policies that can be applied.

As a workaround, you can apply the access policy using the following TMSH command:

tmsh modify apm profile access <profile-name> generation-action increment

Prepend the <profile-name> with the folder name of the app. For example, if you deployed an application using the name "apiProtection101", the command to run would be:

tmsh modify apm profile access apiProtection101.app/apiProtection101_ap generation-action increment
760946 When you create a configuration with SAML metadata file, and then upgrade the Guided Configuration, the configuration fails to deploy. This occurs because the metadata file after the upgrade is not found in the desired location.

As a workaround, upload the metadata file again using a different file name before deploying the configuration.

761669 The API Protection Proxy configuration currently supports the maximum number of 500 user groups. Configuring a configuration with 500+ user groups would result in unexpected behavior.
766073 The API Protection Proxy configuration deployed on the Guided Configuration version 4.1 fails to redeploy after upgrading to version 5.0. As a workaround, undeploy the configuration and deploy it again.
767845 On BIG-IP i5800 with APM and AVR provisioned, deploying an API Protection Proxy configuration with 200+ rate limiting overrides or 200+ whitelist/blacklist entries, may result in the following error message:

error : transaction failed:<transaction_number>: The requested API Protection Profile (/<partition path>/<profile name>) already exists in partition Common.

As a workaround, use TMUI when adding a large number of rate limiting overrides or whitelist/blacklist entries.

768041 The Exchange Proxy configuration deployed on the Guided Configuration version 3.0 fails to redeploy after upgrading to version 5.0. As a workaround, undeploy the configuration and deploy it again.
768069 The OAuth Authorization Server configuration deployed on the Guided Configuration version 4.1 fails to redeploy after upgrading to version 5.0, giving the following error message:

error : transaction failed:<transaction_number>: Cannot delete customization group (/Common/OauthServer.app/OauthServer_act_logon_page) because it is used.

As a workaround, undeploy the configuration and deploy it again.
768093 The Logon Protection configuration deployed on the Guided Configuration version 4.1 fails to redeploy after upgrading to version 5.0. As a workaround, undeploy the configuration and deploy it again.
769365 The API Protection Proxy configuration deployed on the Guided Configuration version 4.1 on the BIG-IP 14.1.0 system fails to redeploy after BIG-IP is upgraded to version 15.0, giving the following error message:

error : transaction failed:<transaction_number>: The requested API Protection Profile (/<partition path>/<profile name>) already exists in partition Common.

As a workaround:
  1. Export the API Protection Proxy configuration on the BIG-IP 14.1 system.
  2. Upgrade the BIG-IP system to version 15.0.
  3. Import the exported configuration.
  4. Redeploy the configuration.
Note: If you also have Advanced WAF licensed and provisioned, you would require an additional step of undeploying and redeploying the application after importing the configuration on step 3.
790109 When an API Protection Proxy configuration is created with HTTP Basic Auth and HTTP Basic SSO, then the connection fails, giving the following error in the logs:

Could not find SSO username, check SSO credential mapping agent setting

814549 When the API Protection Proxy configuration is configured and an LDAP Query is selected, the resulting deployed policy does not contain the LDAP Query Agent.
823849 The Oauth Authorization Server configuration deployed on the Guided Configuration version 4.1 fails to redeploy after upgrade to version 6.0. As a workaround, undeploy the configuration and deploy it again.
823869 When the API Authorization with OAuth and F5 as OAuth Client and Resource Server configurations are deployed using the Create New option to select a DNS Resolver, then the configurations fail to redeploy. This happens because the Choose DNS Resolver setting continues to have the Create New option selected and does not use the existing DNS resolver created earlier.

As a workaround, select the existing DNS resolver before redeploying.

831621 The SAML Identity Provider for Applications and Oauth Authorization Server configurations deployed on the Guided Configuration version 5.0 fails to redeploy after upgrade to version 6.0. As a workaround, undeploy the configuration and deploy it again.
835169 When you update the External IdP Connector settings for a deployed SAML Service Provider configuration and redeploy, the old IdP connector settings are not replaced with the new settings. When you access the service provider configuration using Access > Federation > SAML Service Provider > Local SP Services, you receive the following error: Error: could not find an IdP connector for saml aaa server that matches IdP selection criteria

As a workaround, undeploy the configuration and deploy it again.

Known issues with Guided Configuration for BIG-IP Advanced Web Application Firewall

The following are known issues that affect Guided Configuration for BIG-IP Advanced Web Application Firewall.

ID number Description
714573 New policies cannot be deployed when the device is at the full workload. Trying to deploy a policy at such time generates a Timeout error. The existing deployed policies are not affected. Wait until the load on the device decreases and then deploy new policies.
719842 The Guided Configuration cannot activate Behavioral DoS after the failover of an HA configuration while the standby node is active. Behavioral DoS can be activated by the guided configuration only after the initial node recovers, and the HA state is resolved.
725507 After deploying a Web Application Firewall configuration, the "Differentiate between HTTP/WS and HTTPS/WSS URLs" checkbox cannot be edited in the Guided Configurations interface. This checkbox can be edited from the BIG-IP UI.
748910 After a failover on a multi-blade chassis, some guided configurations are sometimes not available for viewing or editing. To view or edit all configurations after a failover:
  1. Log in to the BIG-IP device via SSH.
  2. Run the following command: cd /var/config/rest/iapps/
  3. Run the following command: rm -rf f5-iappslx*
  4. In the BIG-IP UI, navigate to Security > Guided Configuration. The guided configurations will reinstall for viewing and editing.
748912 After a failover on a multi-blade chassis, the following error message may sometimes appear when attempting to access the guided configurations:

error: The requested URL /iapps/f5-iappslx-waf-app-comp-protection/index.html was not found on this server.

To successfully access the guided configurations:
  1. Log in to the BIG-IP device via SSH.
  2. Run the following command: cd /var/config/rest/iapps/
  3. Run the following command: rm -rf f5-iappslx*
  4. In the BIG-IP UI, navigate to Security > Guided Configuration. The guided configurations will reinstall for viewing and editing.
752179 Attempting to deploy a Bot Protection configuration imported from a BIG-IP device to a BIG-IP device running a different BIG-IP version deploys successfully, and then returns error messages. To successfully deploy this configuration without error messages:
  1. Open the imported configuration.
  2. Make any change to the configuration.
  3. Save the modified configuration and redeploy.
752556 When you deploy the REST API security (Open API Spec) configuration and then disable the Managed Configuration feature, the Apply Access Policy link is shown in the upper left of the AGC screen. The user will not be able to apply the policy using this link as clicking this link opens an empty list page, which normally would display the name of access policies that need to be applied.

As a workaround, you can apply the access policy using the following TMSH command:

tmsh modify apm profile access <profile-name> generation-action increment

Prepend the <profile-name> with the folder name of the app. For example, if you deployed an application using the name "apiSecurity101", the command to run would be:

tmsh modify apm profile access apiProtection101.app/apiProtection101_ap generation-action increment
754672 When you click on Guided Configuration or navigate back and forth too many times after navigating to other BIG-IP menus, the page stops running JavaScript and fails to render in Internet Explorer giving an out of memory error.
As a workaround:
  • Reload the page by refreshing the browser tab or window.
  • Close all Internet Explorer browser instances, restart the browser and navigate to Guided Configuration again.
761669 The REST API security (Open API Spec) configuration currently supports the maximum number of 500 user groups. Configuring a configuration with 500+ user groups would result in unexpected behavior.
766597 When you create the Bot Protection configuration or the Web Application Comprehensive Protection configuration with Bot Defense enabled, the newly created configurations are not displayed in the iApps > Application Services > Applications list. You can view the configuration either from the Guided configuration summary page or by navigating to iApps > Application Services > Applications LX.
767845 On BIG-IP i5800 with APM and AVR provisioned, deploying a REST API security (Open API Spec) configuration with 200+ rate-limiting overrides or 200+ whitelist/blacklist entries, may result in an error message. As a workaround, use TMUI when adding a large number of rate-limiting overrides or whitelist/blacklist entries.

Fixed issues in Guided Configuration for BIG-IP Access Policy Manager

The following are fixed issues in this version of Guided Configuration for BIG-IP Access Policy Manager.

ID Number Description
720065-3 Fixed the issue where a redeployment failed with an error message when the application required a file but was not provided before deployment:

error : transaction failed:<transaction_number>: file <file_path> expected to exist.

722774-1 Previously, you could not configure a client certificate check and Workplace Join in the same ADFS Guided Configuration use case. This issue has been fixed, and now the connections to ADFS is successful.
723642-1 Previously, Guided configuration could get into a state where the configuration could not be deployed, undeployed, or deleted. This issue is now fixed.
763233 Previously, unlocking and re-locking a deployed API Protection Proxy configuration resulted in an error message, following which you could not undeploy or delete the configuration. This issue has been fixed, and now you can unlock and re-lock the deployed configuration without any error.
769765 Previously, the API Protection Proxy configuration deployed with Rate Limiting override failed to redeploy after deleting the override and gave an error. This issue has been fixed, and now you can redeploy without any error.
778381 Previously, when the Trusted Certificate Authorities for Client Authentication certificate is updated in a deployed Identity Aware Proxy configuration and redeployed, it did not update and remained the same. This issue has been fixed, and now the certificate is updated successfully.
793305 Previously, specifying a route domain with more than three digits in the Destination Address for a Virtual server, gave an error. This issue has been fixed, and now the valid range for route-domain is 0-65534.
814201 Previously, the API Protection Proxy configuration configured with LDAP may have missing SearchDN, SearchFilter, UserDN, and Show Extended Errors LDAP authentication properties. This issue has been fixed, and now the LDAP properties are present in the LDAP Auth agent of the deployed policy.
835121 Previously, in some cases, when a file with special characters in the file name was uploaded, Guided Configuration would freeze. This issue has been fixed, and now a file name with special characters and spaces can be uploaded successfully.

Fixed issues in Guided Configuration for BIG-IP Advanced Web Application Firewall

The following are fixed issues in this version of Guided Configuration for Advanced Web Application Firewall.

ID Number Description
763233 Previously, unlocking and re-locking a deployed REST API security (Open API Spec) configuration resulted in an error message, following which you could not undeploy or delete the configuration. This issue has been fixed, and now you can unlock and re-lock the deployed configuration without any error.
769765 Previously, the REST API security (Open API Spec) configuration deployed with Rate Limiting override, failed to redeploy after deleting the override and gave an error. This issue has been fixed, and now you can redeploy without any error.

Contacting F5

North America 1-888-882-7535 or (206) 272-6500
Outside North America, Universal Toll-Free +800 11 ASK 4 F5 or (800 11275 435)
Additional phone numbers Regional Offices
Web http://www.f5.com
Email support@f5.com

Additional resources

You can find additional support resources and technical documentation through a variety of sources.

F5 Support

https://f5.com/support :: Self-solve Options

Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.

AskF5 Knowledge Base

https://support.f5.com/csp/home

The storehouse for thousands of knowledgebase articles that help you manage your F5 products more effectively. Whether you want to browse periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.

BIG-IP iHealth Diagnostics and BIG-IP iHealth Viewer

https://f5.com/support/tools/ihealth

BIG-IP iHealth Diagnostics identifies issues, including common configuration problems and known software issues. It also provides solutions and links to more information. With BIG-IP iHealth Viewer, you can see the status of your system at-a-glance, drill down for details, and view your network configuration.

F5 DevCentral

https://devcentral.f5.com/

Collaborate and share innovations including code samples, new techniques, and other tips, with more than 300,000 F5 users worldwide. DevCentral is the place to ask questions, find solutions, learn to harness the power of F5’s powerful scripting language, iRules, and much more.

Communications Preference Center

https://interact.f5.com/F5-Preference-Center.html

Here, you can subscribe to a number of communications from F5. For information about the types of notifications F5 provides, see K9970: Subscribing to email notifications regarding F5 products.