-
Traffic by network selection on portal [DDoS & Transit Services > DDoS Protection]
Add the possibility of selecting one of our networks in the portal in the DDOS protection section, because today we can only see the graph of one of our networks.0
-
Load Balance between RE and CE
Leave the application accessible through RE and CE, so if the RE suffers any unavailability, access to the application will go through the CE F5XC instance via the internet. Not leaving the application unavailable.0
-
Allowed for multiple SSO providers
Distributed Cloud customers often have multiple directories that they would like to link to a single tenant. For example, a customer may have one AAD environment for Dev, and another for Prod. Or some may have PCI, and non-PCI.2
-
F5 XC Bot Defense iApp - Traffic Analyzer Cloud Console - More Details
To better evaluate with APP Owner the management of any false positive of the Solution, according to us, it should be important to applicate more details on every request that we can see on Traffic Analyzer Cloud Console part. At the moment we can...0
-
GLR not logging req_headers for request logs - shows null
GLR not logging req_headers for request logs. Value shows null. Only security logs shows all req_headers and not a null value0
-
Allow pod to pod communication across namespace on AppStack
By default, AppStack doesn't allow pod to pod communication across namespaces. When pod need to talk to another pod on different namespace, it require to go via the service layer / service cluster IP. This create a challenges for apps that require...
0
-
Show parent objects button
Description: As done for "Show child objects", create a button "Show parent objects" Use case: When a monitor object is deleted with an error "2 objects attached", enduser would like to know which pool objects are attached to this monitor. Today, ...0
-
CE to prefer AWS NLB endpoint in the same AZ to reduce inter-AZ data transfer costs
For an AWS VPC site cluster of 3 nodes (1 CE in each AZ), when defining an origin pool with the following details: Type: DNS Name of Origin Server on given Sites DNS Name: <AWS NLB FQDN, e.g. my-nlb-123456789012.us-west-2.elb.amazonaws.com> ...0
-
Add VxLAN option to Site Mesh Groups for layer-2 support between sites
Ran into customer scenario where the requirement was to have two CE sites share the same network address space. VxLAN would have been helpful. <local_net 172.28.1.0/24> -- [CE1] ===[XC]===[CE2]--<local_net 172.28.1.0/24>1
-
WAF exclusion rule to be reused by multiple LB
Customer doing PoC and request to re-use WAF exclusion rules in a global level, as current settings require customer to create WAF exclusion policy on LB level.0