# Third Party Module signature validity

**URL:** <https://forum.inductiveautomation.com/t/third-party-module-signature-validity/19624>\
**Category:** 3rd Party Modules\
**Created:** [September 11, 2018, 3:03pm UTC](https://forum.inductiveautomation.com/t/third-party-module-signature-validity/19624 "2018-09-11T15:03:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![m.furundarena](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@m.furundarena](https://forum.inductiveautomation.com/u/m.furundarena)\
**Post date:** [September 11, 2018, 3:03pm UTC](https://forum.inductiveautomation.com/t/third-party-module-signature-validity/19624/1 "2018-09-11T15:03:38Z")

</div>

We develop a module in Java for Ignition 7.8.4, so a code signing certificate is needed. Our code-signing certificate has 3-year validity.

According to our software developer, the module will run for 5-years after signature. However, we cannot find where do the 5-years validity come from.

Could you confirm the 5-year validity?

Thank you in advance.

Kind regards,

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [September 11, 2018, 3:08pm UTC](https://forum.inductiveautomation.com/t/third-party-module-signature-validity/19624/2 "2018-09-11T15:08:03Z")

</div>

The 5-year validity period is embedded information in your code signing certificate, signed by whatever CA you got it from.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 11, 2018, 3:37pm UTC](https://forum.inductiveautomation.com/t/third-party-module-signature-validity/19624/3 "2018-09-11T15:37:36Z")

</div>

Ignition doesn’t use the expiration of the certificate to kill an installed module. It does reclassify such modules as self-signed in the gateway web interface when the cert runs out. When I renewed my code signing cert this spring, I rebuilt all of my modules to sign with the new cert, to avoid newcomers and upgraders getting a warning on install.