# Signed Module listed with 'Unknown Author'

**URL:** <https://forum.inductiveautomation.com/t/signed-module-listed-with-unknown-author/83075>\
**Category:** Module Development\
**Created:** [December 13, 2023, 10:49am UTC](https://forum.inductiveautomation.com/t/signed-module-listed-with-unknown-author/83075 "2023-12-13T10:49:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Darren\_Steele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/darren_steele/32/55624_2.png) [@Darren\_Steele](https://forum.inductiveautomation.com/u/Darren_Steele)\
**Post date:** [December 13, 2023, 10:49am UTC](https://forum.inductiveautomation.com/t/signed-module-listed-with-unknown-author/83075/1 "2023-12-13T10:49:17Z")

</div>

Hi all,

Not sure if it's something I can control on my side but when I sign a module and install it on my local gateway it comes up as belonging to "Unknown Author". Did I miss something in the POM? Is this a config change on the IA side?

Thanks for any help

---

<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:** [December 13, 2023, 1:44pm UTC](https://forum.inductiveautomation.com/t/signed-module-listed-with-unknown-author/83075/2 "2023-12-13T13:44:11Z")

</div>

I think it means both the vendor name in the module.xml file _and_ the CN of your signing cert are empty/missing.

---

<div class="post-metadata">

**Author:** ![Darren\_Steele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/darren_steele/32/55624_2.png) [@Darren\_Steele](https://forum.inductiveautomation.com/u/Darren_Steele)\
**Post date:** [December 13, 2023, 5:46pm UTC](https://forum.inductiveautomation.com/t/signed-module-listed-with-unknown-author/83075/3 "2023-12-13T17:46:54Z")

</div>

Thanks Kevin. Turns out the signing cert had expired! All solved now 🙂
