Did you know that your internet is out of date?

Your browser is out of date, and may not be compatible with our website.

Just click on the icons to download a compatible browser. 

Close this window

By closing this window you acknowledge that your experience on this website may be degraded. 

Outage Notification: On Saturday, June 5,12:30-2:30 p.m. EDT (6:30 to 8:30 p.m. UDT), this website will undergo planned maintenance. Thank you for your patience.
Nov 12


Niagara 4.9 Module Signing

Learn about module signing requirements in 4.9, how to sign modules and the benefits of code signing. Code signing is the process of applying a digital signature to a piece of code so that it can be later verified to ensure that it has not been modified after it was signed. This can help establish that the code came from a trusted source and reduce the risk of installing malicious code. In Niagara, all stock modules are signed and verified at runtime. In Niagara 4.8 and later, there is added support for the signing and verification of third party modules. Third party module signing is still optional in most cases, but this will gradually shift to a requirement over the course of future releases. By using module signing with Niagara you can ensure enhanced security and the integrity of your system. Join the TridiumTalk to learn more! Product manager Michael Smith and Software Engineer Patrick Sager will discuss code signing practices and benefits, module signing requirements in 4.9 and beyond, and will demonstrate how to properly sign modules. Through this demonstration, participants will possess a deeper understanding of code signing, signing requirements, installing signed modules, signing modules in Workbench, and signing modules in the Niagara development environment.


Nov 12 - Nov 12, 2020
Related files