# Module Signing

**URL:** <https://forum.inductiveautomation.com/t/module-signing/12144>\
**Category:** 3rd Party Modules\
**Created:** [September 21, 2016, 4:35pm UTC](https://forum.inductiveautomation.com/t/module-signing/12144 "2016-09-21T16:35:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nifemi](https://avatars.discourse-cdn.com/v4/letter/n/a5b964/32.png) [@nifemi](https://forum.inductiveautomation.com/u/nifemi)\
**Post date:** [September 21, 2016, 4:35pm UTC](https://forum.inductiveautomation.com/t/module-signing/12144/1 "2016-09-21T16:35:38Z")

</div>

Module Marketplace has become Module Showcase, and It seems I can no longer get developer license keys, or sign a module for internal use… have I missed something?

Thanks.

---

<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 21, 2016, 5:49pm UTC](https://forum.inductiveautomation.com/t/module-signing/12144/2 "2016-09-21T17:49:30Z")

</div>

Module signing has changed starting in 7.7.8, 7.8.3, and 7.9.0 to allow developers to sign their modules with their own certificate. You can use either a self-signed certificate or a code signing certificate from a CA of your choice. The difference is in what is presented to the end user during the module installation process.

The technical details you need to get stared with the new module signing can be found here: [docs.inductiveautomation.com:84 … le+Signing](https://docs.inductiveautomation.com:8443/display/SE/Module+Signing)

As far as developer licenses go, you will need to get them through your sales rep. You shouldn’t need licenses so often that this becomes burdensome. Additionally, I think starting in 7.8.4, there’s now a flag you can pass to the JVM on startup that allows unsigned modules to be installed for development purposes, which is the primary reason people needed the developer licenses in the first place. Add an additional startup parameter to ignition.conf: -Dignition.allowunsignedmodules=true

---

<div class="post-metadata">

**Author:** ![nifemi](https://avatars.discourse-cdn.com/v4/letter/n/a5b964/32.png) [@nifemi](https://forum.inductiveautomation.com/u/nifemi)\
**Post date:** [September 23, 2016, 2:35pm UTC](https://forum.inductiveautomation.com/t/module-signing/12144/3 "2016-09-23T14:35:05Z")

</div>

Thanks, Kevin.

Developer licences are really not a problem, and it sounds like the new module signing method may be more convenient. Of course, I’ve basically been hiding from the new internal db structure, avoiding changing over… that had to end sometime 🙂

---

<div class="post-metadata">

**Author:** ![Van.den.Maegdenbergh](https://avatars.discourse-cdn.com/v4/letter/v/87869e/32.png) [@Van.den.Maegdenbergh](https://forum.inductiveautomation.com/u/Van.den.Maegdenbergh)\
**Post date:** [April 30, 2018, 7:42pm UTC](https://forum.inductiveautomation.com/t/module-signing/12144/4 "2018-04-30T19:42:12Z")

</div>

Hi, as kevin pointed out you can add the necessary additional startup parameter by adding the following line in  
the ignition.CONF file:

> wrapper.java.additional.7=-Dignition.allowunsignedmodules=true