To configure a policy for signed Eclipse plug-ins, complete the following fields on the Domino Administrator client Signed Plugins tab.

To configure a policy for signed Eclipse plug-ins, complete the following fields on the Domino® Administrator client Signed Plugins tab. The options for each of the following fields are to ask the user, never install, or always install.

• Installation of plug-ins that are expired or not yet valid
• Installation of unsigned plug-ins
• Installation of plug-ins signed by an unrecognized entity
• Domino policy takes precedence over Eclipse preferences. Eclipse preferences reside in the plugin_customization.ini file.

  Note: Features and plug-ins being deployed to an existing Notes install, for example using a widget, should be signed by a trusted certifier.

  Administrative 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. See Using Domino policy to set or verify trust for details.

  Note: Alternatively, administrative trust defaults can be configured as part of the deploy.nsf in an install kit or in an installed deploy.nsf on disk. See Customizing an install kit to set certifier and trust defaults for details.

Related tasks
Signing custom or third-party features and plug-ins for install and update
Creating a security policy settings document
Customizing Notes install for features and plug-ins on Windows and Mac

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Feedback on Help or Usability?

Help on Help