Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

DSDP/MTJ/Requirements/Signing/keystore management

< DSDP‎ | MTJ‎ | Requirements
Revision as of 07:21, 5 March 2009 by Wtv368.motorola.com (Talk | contribs) (Core)

Core

This section lists the main core requirements for the Keystore Management feature.

ID: sign:FR001 - MTJ shall define an extension point where third parties can add their APIs' security permissions to MTJ permission set.

Description: MTJ requires a set of security permissions to sign Java ME applications. These permissions are defined by mobile APIs. The standard APIs' permissions are shipped within MTJ, although there must be a way for third party vendors to add their APIs' security permissions to MTJ, in order to make these permissions available during the sign process. As such, a new extension point must be created enabling the inclusion of these new permissions.

The extension point will be composed by the following elements:

  • class
    • name (String Attribute) [REQUIRED]

      Description: The name of the class requiring a permission.

    • sequence [1;n] (permission) [REQUIRED]

      Description: One or more entries for all class required permissions.

  • permission
    • name (String Attribute) [REQUIRED]

      Description: The name of the class required permission.

Priority: 1

Owner: David Marques

Status: Proposed on 02-Mar-2009

Community Review: TBD

Related Bugs: bug 261522


ID: sign:FR002 - Changes between keystore management implementations must be transparent to the rest of the system.

Description: An interface must be defined for the keystore management entity since it might have several implementations available in order to support different environments.

Priority: 1

Owner: David Marques

Status: Proposed on 02-Mar-2009

Community Review: TBD

Related Bugs: bug 261522


User Interface

This section lists the main User Interface requirements for the Keystore Management feature.

ID: sign:FR002 - MTJ shall have a 'signing' page on the JAD editor for signing purposes

Description: The 'signing' page on the JAD editor will enable user to do the following tasks:

  • Manage required permissions (add/remove/order/scan)
  • Manage optional permissions (add/remove/order/scan)
  • Select the key alias to use for signing

NOTE: Scan used on the first two tasks above means scanning the code in in order to find the required permissions.

Priority: 1

Owner: David Marques

Status: Proposed on 02-Mar-2009

Community Review: TBD

Related Bugs: bug 261521

Related Images: JAD Editor page


ID: sign:FR003 - MTJ shall add "MIDlet Suite Signing" page to the preferences under "Java ME"

Description: The "MIDlet Suite Signing" page on the preferences under "Java ME" will enable user to manage:

  1. Keystore
  2. Key Alias
  3. Generate CSRs
  4. Import certificates

Priority: 1

Owner: David Marques

Status: Proposed on 02-Mar-2009

Community Review: TBD

Related Bugs: bug 261524

Related Images: Preference page (Image 1)
Related Images: Preference page (Image 2)
Related Images: Preference page (Image 3)


ID: sign:FR004 - MTJ shall enable the user to select a Key Alias on the Sign Property Page

Description: MTJ shall enable the user to select a Key Alias from the current keystore on the Sign Property Page.

Priority: 1

Owner: David Marques

Status: Proposed on 02-Mar-2009

Community Review: TBD

Related Bugs: bug 261525

Related Images: Properties page


Back to the top