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 "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...) |
|||
| 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. | ||
Revision as of 15:30, 23 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.