Bug #11512

f5: certificate/key replacement must occur in one resource.

Added by Nan Liu 5 months ago. Updated 3 months ago.

Status:Closed Start date:12/20/2011
Priority:Normal Due date:
Assignee:Nan Liu % Done:

0%
Category:f5 Spent time: -
Target version:-
Keywords: Branch:
Votes: 0

Description

If f5_cert and f5_key for the same cert are treated separately, the device won’t replace the certificate when the new key/cert doesn’t match the old key/cert:

failed: Exception caught in Management::urn:iControl:Management/KeyCertificate::key_import_from_pem()
Exception: Common::OperationFailed
  primary_error_code   : -14 (0xFFFFFFF2)
  secondary_error_code : 0
  error_string         : Keys do not match

In this case, we need to replace the key/cert in one step. It might make more sense to have just f5_keycert or the other possibility is to allow replacement of replace_keycert => true.

History

#1
Updated by Nan Liu 3 months ago

  • Status changed from Accepted to Closed

Fixed.

Also available in: Atom PDF