Dynamic change of HTTPS certificates

Idea ID 2850315

Dynamic change of HTTPS certificates

Within NNMi we have first devices which can be polled by the REST API (eg: Cisco ACI and I think with the 2020.11 release also Meraki Dashboards). In my personal opinion more and more devices will need to be polled in different ways then SNMP.

When working with HTTPS API's we need to provide NNM with the certificate. Usually - when a not self-signed certificate is used - those have a limited time of validity, for example 2-4 years.

According to the support the process to currently replace such a certificate:

  1. Inventory > Web Agents > Select an agent
  2. In “Trusted Certificates” delete the entry
  3. Upload the new certificate
  4. Once applied for all “Web Agents” restart NNM
  5. Check the communication with the APICs.

This feature request is to enhance NNM in such a way, that it is possible to replace certificates of web-agents without restarting the whole NNM. This is rather a big impact for such a minor issue.

1 Comment
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

The idea has received an initial review to ensure adherence to our idea submission and community guidelines. More information may be needed at this stage, and we expect the community to help prioritize the idea with comments and community support (votes/kudos).

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.