While self signing modules using java -jar module-signer.jar \ -keystore=/keystore.jks -keystore-pwd= -alias= -alias-pwd= -chain=/cert.p7b -module-in=/my-unsigned-module.modl -module-out=/my-signed-module.modl as given in the SDK documentation, how to get chain path /cert.p7b? I don't…

Got it! Its working ! I think the problem was the name for the keystore file which was .keystore by default, which I changed to some some thing else, or it could be case sensitivity of the alias name which was different in the command line than as defined in the editor tool! Whatever it is , its wo…

Looks okay to me. Since I can’t reasonably inspect your KeyStore the only thing I can assume is that the KeyPair inside was not created correctly, or didn’t get created using RSA, or you’re using the wrong alias.

hmm....Let me try some more things on my own. Hopefully I would be able too figure it out soon. Best Regards

Now that module signing is working, how to put the Licensing and documentation information in .modl files? Earlier version had an HTML page for documentation & Licensing information. Also hope self signed modules will suffice for putting in module showcase?

Licensing and documentation hasn’t changed. The module.conf file must have a <Licence> section specifying the file name of the license document, typically license.html, in the root of the .modl file. A <Documentation> section similarly specifies the top level html file of your documentation, or a …

Thanks a lot for the reply. What about self signed models , are they acceptable in module showcase ? Kevin McCluskey has also created a module Showcase API project in Ignition which has text section for Module Info and Module License. Where does this info go? Directly on the Module Showcase page? …

[image] pturmel: The module.conf file must have a <Licence> section specifying the file name of the license document, typically license.html, in the root of the .modl file. A <Documentation> section similarly specifies the top level html file of your documentation, or a PDF file. This is assum…

How are modules to be distributed for evaluation? Do we include the signed .modl files in our downloads? Does the License Key management have to be done by us using the tool supplied by Ignition on 15/09/2015 for all versions of Ignition, or only for 7.9 and above? Then how licenses are managed for…

[image] PRAMANJ: The modl file is generated by maven Sorry, I still use ant, so I can build modules that support many versions of Ignition. The only maven project in my dev box is the module-signer tool. /-: [image] PRAMANJ: How are modules to be distributed for evaluation? Do we includ…

[image] pturmel: Sorry, I still use ant, so I can build modules that support many versions of Ignition. The only maven project in my dev box is the module-signer tool. /-: Thanks a lot Phil. So I will be able to include the self signed modl files in my downloads. I will give you and kyle th…

I got the answer to my previous quest. Another question, how to find out if our module is Licensed or not. (Like the isFreeModule(), is there any function that returns the Licensed status of our modl?). I mean a flag to determine whether the License is activated or still its trial version?

Inductive Automation Forum

Module signing tool

Module Development

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled