Bug ID 517613: ClientSSL profile might have the wrong key/certificate/chain when created with a specific set of steps

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1

Fixed In:
12.0.0, 11.6.1 HF1, 11.5.4 HF2

Opened: Apr 10, 2015
Severity: 2-Critical
Related AskF5 Article:
K15261745

Symptoms

ClientSSL profile might have the wrong key/certificate/chain when created with a specific set of steps.

Impact

GUI shows the right key/certificate/chain in p2, whereas tmsh shows p2 to have default key and certificate.

Conditions

Create a ClientSSL profile (p1) with user-defined key/certificate/chain. Create another clientSSL profile (p2) with all default fields. Modify p2 to have the defaults from p1.

Workaround

None.

Fix Information

ClientSSL profile now has the correct key/certificate/chain when multiple profiles are created with differing key/certificate/chain values.

Behavior Change