Code-signing warning and forced code signing

By default, program object signing is not currently (September, 2017) enforced, but will be enforced in a future version of the framework. The version in which program object signing will be enforced is yet to be determined.

Loading or running any objects you have created without signatures causes the following warning to appear in Application Director:

WARNING [date] Program not signed. The ability to run unsigned programs will be removed in a future release.

where [date] is replaced by today’s date and time.

To override the current default, and require program objects to be signed when they run, configure your station to run with the system property program.requireSigning=true. You configure this property in the system.properties file. When set to true, the system fails to load any unsigned program object or any signed object with a certificate that is not trusted. Program modules are exceptions to this rule.

When a program object with a certificate that is not trusted fails to load, the system adds the certificate to the User Trust Store placing a red shield with a white X to the left of the certificate row. To create an exception for the certificate, click the Approve button. Consider this as a temporary convenience that enables you continue to use the system before your code-signing certificate is officially signed by an intermediate certificate or the root certificate of a Certificate Authority.