Cisco Bug: CSCum50151 - Old tomcat trust certificates still present after hostname change
Mar 08, 2018
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases