Setting Signers of a Deployment Package

The Deployment Package Editor of mToolkit supports signing of generated deployment packages by calling the jarsigner tool (<jdk_home>/bin/jarsigner.exe) of your JDK.

If you will sign your deployment package, first you have to specify the alias representing the signer's keys and own certificate and the keystore to take the signer's keys and own certificate from. A single deployment package might be signed by more than one signer. Then, when building the package out of its Deployment Package Project file, the Deployment Package Editor will check if there are signers specified for the package. If you have assigned such, the editor will call the jarsigner tool to sign the package archive by using the specified signer information.

To specify the security information related to a signer:

  1. In the navigation view (e.g. Package Explorer), locate and open the Deployment Package Project (.dpp) file for the target deployment package by using the Deployment Package Editor.
  2. Go to the Certificates tab of the Deployment Package Editor.
  3. Add a new entry to the table for each signer which will sign the deployment package archive file:
    1. Click the New button.
    2. In the empty row that appears in the table, specify the following properties of the signer:
      • Alias - Type the alias of the signer entity for the keystore keeping its certificate and key pair.
      • Keystore - Specify the location of the keystore file containing the signer's certificate and key pair. Use the Browse (...) button shown in the field to browse the local file system and locate the keystore file (with expected extension .keystore), or type the keystore location by hand.
      • Store Password - Type the password for access to the keystore.
      • Key Password - Type the password for access to the key pair associated with the singer's alias.
      • Store Type - Select the type of the keystore - available values are jks, pkcs11 and pkcs12, or if needed type another keystore type (it should be supported by the used jarsigner).

        Make sure the format of the keystore file you specify matches the Store Type value.





      Figure 1: Specifying signers of the deployment package.
  4. (Optional) Check the Also sign bundles included in the package option, if you want to use the jarsigner tool to also sign the available bundle resources when generating the new deployment package.

    Note: This feature is not supported for exporting an Ant buildfile for future deployment package generation.

  5. Save the Deployment Package Project file in order to keep the changes on signer data.

The signer information will be used in subsequent generation of the deployment package either by using the Quick Build command or by using the Deployment Package part of the Export Wizard.

Note: Make sure you have specified correct path to the jarsigner executable in the mToolkit preference page before generating the deployment package file. Otherwise, the deployment package will not be signed.

Tip: If you do not specify keystore password(s) and/or key password(s), when generating the relevant deployment package, a dialog is displayed prompting you to enter the missing password(s). Passwords entered in this way are not permanently saved in the Deployment Package Project file.


Figure 2: Specifying a signer key password at package generation.

Deployment Package Overview
Deployment Package Editor

Creating a Deployment Package Project File
Configuring Deployment Package Editor
Generating a Deployment Package
Quick Deployment Package Build