Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "E4/EAS/Authentication"
(New page: Status: no progress yet A component should be able to request authentication in a way that the end user perceives as consistent. Since each back end will have different requirements with...) |
(→Eclipse 3.x API) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
See also: [http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/Gadgets-API-Specification.html#rfc.section.5.2.2.3.3 OAuth in the OpenSocial Gadgets spec] | See also: [http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/Gadgets-API-Specification.html#rfc.section.5.2.2.3.3 OAuth in the OpenSocial Gadgets spec] | ||
| + | |||
| + | ==Eclipse 3.x API== | ||
| + | The org.eclipse.equinox.security and other associated bundles provides an authentication mechanism for the storage of passwords. | ||
| + | *[http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.user/reference/ref-securestorage-start.htm Secure storage reference] | ||
| + | *[http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/secure_storage.htm Secure storage development overview] | ||
| + | *[http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/secure_storage_dev.htm Developing with Secure Storage] | ||
| + | *[http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.user/reference/ref-securestorage-works.htm How secure storage works] | ||
| + | *[http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/secure_storage_architecture.htm Secure Storage Architecture] | ||
| + | |||
| + | ==e4 (Java)== | ||
| + | Need to review the [[Architecture Council/Minutes May 15 2008#Sessions, Role-based Access and Security |AC's meeting minutes]] prior to the creation of this e4 API. | ||
Latest revision as of 11:35, 26 October 2009
Status: no progress yet
A component should be able to request authentication in a way that the end user perceives as consistent.
Since each back end will have different requirements with respect to authentication, we probably need to support multiple mechanisms.
See also: OAuth in the OpenSocial Gadgets spec
Eclipse 3.x API
The org.eclipse.equinox.security and other associated bundles provides an authentication mechanism for the storage of passwords.
- Secure storage reference
- Secure storage development overview
- Developing with Secure Storage
- How secure storage works
- Secure Storage Architecture
e4 (Java)
Need to review the AC's meeting minutes prior to the creation of this e4 API.