Bug ID 560890: ClientSSL profiles with same server name should not be assigned to a Virtual Server

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.1.0

Opened: Dec 03, 2015

Severity: 3-Major

Symptoms

ClientSSL profiles with same server name can be assigned to a Virtual Server. This issue was introduced in V11.5.0.

Impact

ClientSSL profile may be wrongly selected due to same server name.

Conditions

no conditions

Workaround

Do not configure ClientSSL profiles with the same server name in a Virtual Server.

Fix Information

An MCP validation is added to check that in a Virtual Server there are no two ClientSSL profiles with same server name. If two ClientSSL profiles with same server name are configured, the following error message will display: 0107149e:3: Virtual server /Common/my_virtual_server has more than one clientssl/serverssl profile with same server name.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips