# Pull request proposal: automatic certificate renewal

**URL:** https://discourse.nodered.org/t/pull-request-proposal-automatic-certificate-renewal/21282
**Category:** Feature Requests
**Created:** [4 February 2020 21:26 UTC](https://discourse.nodered.org/t/pull-request-proposal-automatic-certificate-renewal/21282 "2020-02-04T21:26:45Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [16 February 2020 16:04 UTC](https://discourse.nodered.org/t/pull-request-proposal-automatic-certificate-renewal/21282/12 "2020-02-16T16:04:04Z")

</div>

At this point, there has been no pr raised for us to review or discuss.

The proposal still doesn't quite fit the "clean API" test for me. I don't see why a user should provide the certs in two different ways - both under the HTTPS property and the proposed new refresh function. I think it would be better if it were all under the https setting and the cert properties can either be the cert content itself (as is today), or a function. If it's a function and a refresh interval is also specified under the HTTPS property, then we will call it as needed.

(Yes, on holiday, so response times will be depending on kids and other interesting activities)

---

_[View the full topic](https://discourse.nodered.org/t/pull-request-proposal-automatic-certificate-renewal/21282)._