# SSL certificate expiration notification

**URL:** <https://forum.inductiveautomation.com/t/ssl-certificate-expiration-notification/99367>\
**Category:** Ignition\
**Created:** [December 3, 2024, 3:58pm UTC](https://forum.inductiveautomation.com/t/ssl-certificate-expiration-notification/99367 "2024-12-03T15:58:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ajay\_Gupta](https://avatars.discourse-cdn.com/v4/letter/a/f05b48/32.png) [@Ajay\_Gupta](https://forum.inductiveautomation.com/u/Ajay_Gupta)\
**Post date:** [December 3, 2024, 3:58pm UTC](https://forum.inductiveautomation.com/t/ssl-certificate-expiration-notification/99367/1 "2024-12-03T15:58:21Z")

</div>

Hi,

Does Ignition have in-built feature to send notification email when the gateway SSL certificate is about to expire?

Thanks,  
Ajay

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [December 3, 2024, 4:03pm UTC](https://forum.inductiveautomation.com/t/ssl-certificate-expiration-notification/99367/2 "2024-12-03T16:03:26Z")

</div>

No.

---

<div class="post-metadata">

**Author:** ![Ajay\_Gupta](https://avatars.discourse-cdn.com/v4/letter/a/f05b48/32.png) [@Ajay\_Gupta](https://forum.inductiveautomation.com/u/Ajay_Gupta)\
**Post date:** [December 3, 2024, 4:16pm UTC](https://forum.inductiveautomation.com/t/ssl-certificate-expiration-notification/99367/3 "2024-12-03T16:16:44Z")

</div>

Where is this information stored? Is there a way to put a watchdog on certificates expiration dates and have automation send the notifications?  
Currently we are doing all this manually.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [December 3, 2024, 4:20pm UTC](https://forum.inductiveautomation.com/t/ssl-certificate-expiration-notification/99367/4 "2024-12-03T16:20:10Z")

</div>

With scripting, more or less anything is possible. That said, if you're worried about the public webserver certificate, just set up an external ACME client and be done with it:

> **[Let's Encrypt Guide for Ignition](https://inductiveautomation.com/resources/article/lets-encrypt-guide-for-ignition)**
>
> Ignition 8.0.3 introduces support for hot-reloading the Gateway’s SSL keystore. This capability enables Ignition to play well with services such as Let’s Encrypt which provide for automatic SSL certificate management. This article walks through one...

If you choose not to do that for some reason, you are certainly _able_ to open the Gateway's keystore using scripting, retrieve the certificates, extract the date information, and drive logic from them. Use Java standard library imports if you do.

---

<div class="post-metadata">

**Author:** ![Ajay\_Gupta](https://avatars.discourse-cdn.com/v4/letter/a/f05b48/32.png) [@Ajay\_Gupta](https://forum.inductiveautomation.com/u/Ajay_Gupta)\
**Post date:** [December 3, 2024, 5:49pm UTC](https://forum.inductiveautomation.com/t/ssl-certificate-expiration-notification/99367/5 "2024-12-03T17:49:16Z")

</div>

Thanks @paul-griffith .  
Can you provide a sample code for how i access gateway's keystore?

I am leaning towards that approach.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [December 3, 2024, 5:55pm UTC](https://forum.inductiveautomation.com/t/ssl-certificate-expiration-notification/99367/6 "2024-12-03T17:55:10Z")

</div>

No, because I don't have any. You could ask an LLM for how to "open a Java keystore using Java's standard library in Jython", and you might get something useful-ish. Paths and default passwords for the keystore are in the linked blog post above.
