Guest

Preview Tool

Cisco Bug: CSCum50151 - Old tomcat trust certificates still present after hostname change

Last Modified

Mar 08, 2018

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.5(1.10000.1)

Description (partial)

Symptom:
Run the CLI command "set network hostname", all the certficates are regenerated including Tomcat certificate. All CA signed certificates are replaced with self - signed certificate.
But in the in the tomcat-trust folder (/usr/local/platform/.security/tomcat/trust-certs), the certficate with old hostname is still present though it is  now invalid.

Conditions:
When the hostname is modified.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.