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.
Difference between revisions of "DSDP/MTJ/Requirements/Signing/keystore management"
(→ID: sign:FR001 - MTJ shall define an extension point where third parties can add their APIs' security permissions to MTJ permission set.) |
(→User Interface) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 15: | Line 15: | ||
*'''permission''' | *'''permission''' | ||
** <font color="green"><b>name</b></font> (String Attribute) <font color="#960018"><b>[REQUIRED]</b></font><p>Description: The name of the class required permission.</p> | ** <font color="green"><b>name</b></font> (String Attribute) <font color="#960018"><b>[REQUIRED]</b></font><p>Description: The name of the class required permission.</p> | ||
| + | |||
| + | '''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 | '''Priority:''' 1 | ||
| Line 30: | Line 45: | ||
This section lists the main User Interface requirements for the Keystore Management feature. | This section lists the main User Interface requirements for the Keystore Management feature. | ||
| − | ==='''ID''': sign: | + | ==='''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: | '''Description:''' The 'signing' page on the JAD editor will enable user to do the following tasks: | ||
| Line 54: | Line 69: | ||
---- | ---- | ||
| − | ==='''ID''': sign: | + | ==='''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: | '''Description:''' The "MIDlet Suite Signing" page on the preferences under "Java ME" will enable user to manage: | ||
| Line 79: | Line 94: | ||
---- | ---- | ||
| − | ==='''ID''': sign: | + | ==='''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. | '''Description:''' MTJ shall enable the user to select a Key Alias from the current keystore on the Sign Property Page. | ||
Latest revision as of 07:22, 5 March 2009
Contents
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.
- name (String Attribute) [REQUIRED]
- permission
- name (String Attribute) [REQUIRED]
Description: The name of the class required permission.
- name (String Attribute) [REQUIRED]
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: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:
- Keystore
- Key Alias
- Generate CSRs
- 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: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: bug 261525
Related Images: Properties page