Bug ID 629095: iControl keymanagment impory may fail when stale content exists in /config/ssl

Last Modified: Mar 21, 2019

Bug Tracker

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

Known Affected Versions:
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, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Nov 17, 2016
Severity: 3-Major
Related AskF5 Article:
K08240314

Symptoms

iControl returns fault similar to "Keys do not match" when respective key/cert does not exist in the filestore.

Impact

Unable to import cert/key with particular name while /config/ssl contains stale content.

Conditions

Stale cert/key in /config/ssl which matches the name of the cert/key being imported. For example, iControl attempting to import file as test.crt while /config/ssl/ssl.key contains test.key which does not match test.crt.

Workaround

Remove the conflicting file from /config/ssl/ssl.{key,crt}.

Fix Information

A certificate being imported is now checked against contents in filestore to determine whether the contents in /config/ssl are stale.

Behavior Change