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

Difference between revisions of "DSDP/MTJ/Requirements/Signing/keystore management"

< DSDP‎ | MTJ‎ | Requirements
(User Interface)
(ID: sign:FR003 - MTJ shall have a 'signing' page on the JAD editor for signing purposes)
Line 64: Line 64:
 
'''Community Review:''' TBD  
 
'''Community Review:''' TBD  
  
'''Related Bugs:''' TBD
+
'''Related Bugs:''' {{bug|261521}}
 +
 
 +
'''Related Images:''' [https://bugs.eclipse.org/bugs/attachment.cgi?id=122956  JAD Editor page]
 
----
 
----
  

Revision as of 09:14, 3 March 2009

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 uses a set of security permissions to sign mobile applications, these permissions are defined by the mobile APIs. The standard APIs' permissions are shipped on MTJ, although there must be a way for third party vendors to add their APIs' security permissions to MTJ. In order to make their permissions available for developers to sign their applications the extension point must be extended.

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: TBD


ID: sign:FR002 - MTJ shall scan the project's code and inform all required permissions

Description: MTJ shall scan the project's code and inform all required permissions on the code so the user can select it's required permissions.

Priority: 2

Owner: David Marques

Status: Proposed on 02-Mar-2009

Community Review: TBD

Related Bugs: TBD


User Interface

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

ID: sign:FR003 - 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:FR004 - 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: TBD


ID: sign:FR005 - 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: TBD


Back to the top