Currently NM certificate gets renewed if half of validity passed, however this renewal causes NM service restarted automatically and could cause WP/AS ongoing process failed unexpectedly. Also customer can not control this behaivor and can not restart NM service manually to renew its certificate.
Server only renews its certificate when restarted so customer can do this manually.
Please make NM certificate renewal process as the same as Server.
Implemented in | 10.7 |
Hi Jens,
Thanks.
I confirmed the behavior you mentioned on me end as well.
Please close this.
The certificate renewal changed in 10.7 (backported to 7.11.7 and 10.3.4). In these and later versions an expiration check is done during startup (of both Spotfire Server and Node Manager) and if less than half of the validity of the certificate. The default validity of certificates was also raised from one to two years - which means that for new certificates it's sufficient to restart the process once a year to avoid outages (for older certificates it has to be once every 6 months).
The NM does also, unlike the Spotfire Server, check the expiration when there's two days left of the certificate's validity (and triggers a renewal and a restart if needed) but this can be avoided by restarting the server (every 6 or 12 months).