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 "Password Card"
(→Requirements) |
|||
| Line 10: | Line 10: | ||
b) Adhere to these constraints: | b) Adhere to these constraints: | ||
# No extra UI on the browser chrome (e.g. a toolbar) | # No extra UI on the browser chrome (e.g. a toolbar) | ||
| − | #* Note: Roboform, Google Toolbar require you to click a button on | + | #* Note: Roboform, Google Toolbar require you to click a button on a toolbar |
# Automatically highlights fields that it can fill (like Google Toolbar, Sxipper) | # Automatically highlights fields that it can fill (like Google Toolbar, Sxipper) | ||
#* Browsers do not natively do this | #* Browsers do not natively do this | ||
Revision as of 16:12, 3 March 2009
As is says on the home page:
- A long term goal is that [the Higgins] client offer what might be called "universal login." This is the ability to log you in to almost any website or app (called a Relying Party (RP)) using a variety of methods including I-Card, OpenID and username/password.
This page focuses on the username/password subgoal mentioned above.
Requirements
a) Support these Password Card Use Cases
b) Adhere to these constraints:
- No extra UI on the browser chrome (e.g. a toolbar)
- Note: Roboform, Google Toolbar require you to click a button on a toolbar
- Automatically highlights fields that it can fill (like Google Toolbar, Sxipper)
- Browsers do not natively do this
- Pure superset of the browser's built-in functionality
Open Issues
What Triggers the fill. Alternatives:
- the user must click in username (or password??) field to trigger fill
- automatic - native password managers automatically fill