Following the tutorial : Sign a Module | Ignition SDK Programmer's Guide. Where is the module-signer.jar is? Is it about downloading the zip of code in github and changing the postfix of the folder to .jar? Because it seems there are only .java files within the folder. Apologize for my newbee question. 
I don't have an answer, for you, but your question belongs here. You will get better answers and probably faster here.
You need to check out that repository and build the tool yourself.
1 Like
Hi Kevin, thank you for you help. So far I have prepared the keystore, alias, chain and module. You mean I have to assemble a 'module-signer.jar' using files in the github?
What build system, if any, are you using for your actual module - Maven, Gradle, or something else?
If you're using Maven or Gradle we publish module build tools to public repositories that can both create and sign your module files for you - no need to deal with the module-signer jar directly.
I create my module almost following steps of build module. The code I use for compiling my module is: .\gradlew.bat clean build, so I guess I'm using Gradle? I don't have much knowleadge about Java... And the module it yields have a label 'unsigned' within its file name. The name of module is: ****.unsigned.modl.
There is definitely no information available about signing modules in the build stage in the IA instructions, I went through it a few months back knowing it was feasible but found no details.
The Gradle Ignition module plugin can sign modules (via the module-signer tool), it's discussed in part 3 of the README here: ignition-module-tools/gradle-module-plugin at master · inductiveautomation/ignition-module-tools · GitHub
The Maven Ignition module plugin does not sign modules for you.
2 Likes