Bug ID 1491197: Server Name (TLS ClientHello) Condition in policy shouldn't be allowed when "Enable UDP" option is selected in application under Protocols & Profiles

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(CM) None(all modules)

Known Affected Versions:
20.2.0, 20.2.1

Opened: Jan 16, 2024

Severity: 3-Major

Symptoms

Validation is not available in BIG-IP Next Central Manager for the mutually exclusive configurations "Enable UDP" in application and "TLS ClientHello" condition in SSL Orchestrator policies. When we deploy Application with UDP enabled, then attach SSL Orchestrator policies to the application, it should not have "TLS Client Hello" condition based on "Server Name".

Impact

Traffic processing will not work as the configuration is not valid and will not be sent to TMM until fixed.

Conditions

Below are the condition in sequence: 1. Create an application with UDP enabled 2. Create and Attach an sslo policy, to that application, which has "TLS ClientHello" condition based on "Server Name" and deployed to next instance.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips