NOTES CLIENT INSTALLATION AND UPGRADE
com.ibm.rcp.security.update/UNSIGNED_PLUGIN_POLICY=PROMPT
com.ibm.rcp.security.update/UNTRUSTED_SIGNATURE_POLICY=PROMPT
Note Features and plug-ins being installed as part of Notes install or upgrade must be signed. Features and plug-ins being deployed to an existing Notes install, for example using a widget, should be signed by a trusted certifier.
Note Trust defaults can be pushed to clients using Domino policy settings in the "Administrative trust defaults" page on the security policy document's "Keys and Certificates" tab as well as by using the deploy.nsf. However, if you have used the Keys and Certificates tab on the Security policy dialog to push administrative trust defaults, those settings are used and the user's deploy.nsf is ignored.
By default the Notes installer uses only the keystore in the deploy directory to make trust decisions. If you want to trust any certificate issued by a well known certification authority, use the the following statement to the install kit's deploy\plugin_customization.ini file as below.
Note This instructs the kit installer to verify trust in code signing certificates using the JRE CACERTS file, which contains the certificates for all well known roots. Using this setting will compromise the security of the installer, since anyone with a valid certificate can modify the code.
In the case of untrusted, the user can choose to start trusting the certificate by adding it to the keystore. Note that during Notes installation, PROMPT = DENY, because the installation program does not prompt the user for this information.
The EXPIRED_SIGNATURE_POLICY setting defines the default behavior when provisioning encounters a JAR file that is signed but the certificate used to sign the jar file has expired. The available values are PROMPT, ALLOW, and DENY. For the initial install, PROMPT=DENY because there is no user interface for this function. The PROMPT function is recognized by Notes upgrade.
Note For any install or upgrade performed using an install kit, PROMPT=DENY.
The following example allows JAR files with expired signatures to be installed or updated:
The TSAEXPIRED_SIGNATURE_POLICY setting defines the default behavior when provisioning encounters a JAR file with an expired time stamp. The available values are PROMPT, ALLOW, and DENY. For the initial install, PROMPT=DENY because there is no user interface for this function. The PROMPT function is recognized by Notes upgrade.
The following example allows JAR files with expired timestamp to be installed or updated:
The UNSIGNED_PLUGIN_POLICY setting defines the default behavior when provisioning encounters an unsigned JAR file. The available values are PROMPT, ALLOW, and DENY. For the initial install, PROMPT=DENY because there is no user interface for this function. The PROMPT function is recognized by Notes install and upgrade.
The following example allows unsigned JAR files to be installed or updated:
The UNTRUSTED_SIGNATURE_POLICY setting defines default behavior when provisioning encounters a JAR file that has been properly signed, but no matching certificate exists in the keystore.
The available values are PROMPT, ALLOW, and DENY. For kit install and upgrade, PROMPT=DENY because there is no user interface for this function.
The following example does not allow untrusted JAR files to be installed or updated. If the Notes installer encounters an untrusted signature during initial Notes install, it exits the install with an error.