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 "Security: Requirements"
(New page: Document for collecting Security requirements == Requirements == Support plugging JCA/JCE classes into the platform dynamically via services or extensions Use Java-standard APIs like Ke...) |
|||
| Line 3: | Line 3: | ||
== Requirements == | == Requirements == | ||
| − | Support plugging JCA/JCE classes into the platform dynamically via services or extensions | + | - Support plugging JCA/JCE classes into the platform dynamically via services or extensions |
| − | Use Java-standard APIs like KeyStore, CertStore, etc. where appropriate for Key management | + | - Use Java-standard APIs like KeyStore, CertStore, etc. where appropriate for Key management |
| − | Support login to the platform | + | - Support login to the platform |
| − | Run with a fully-integrated SecurityManager | + | - Run with a fully-integrated SecurityManager |
| + | |||
| + | [[Category:Equinox]] | ||
| + | [[Category:Security|Requirements]] | ||
Revision as of 14:31, 17 May 2007
Document for collecting Security requirements
Requirements
- Support plugging JCA/JCE classes into the platform dynamically via services or extensions - Use Java-standard APIs like KeyStore, CertStore, etc. where appropriate for Key management - Support login to the platform - Run with a fully-integrated SecurityManager