Identity-inputs: Difference between revisions

Identity-inputs (view source)

407 bytes added , 25 June 2011

5

edits

@@ Line 114: / Line 114: @@
 Open issues regarding the above brainstorm proposal. Please add new issues as === subheads.
-=== issue 1: tracking the relevant realms and identities as well ===
+=== issue 1: Do we need to be able to identify the relevant realms and identities in each use case? If so, how will we do that? ===
 For many of the use cases, in order for a password manager to know how to fill out the form correctly, it needs to know not only which elements of the form are relevant and how they are being used, but some amount of currently active state. In particular, we probably need to know which "realm" is relevant for the form, and if an active identity is required, which one is currently active.
@@ Line 121: / Line 121: @@
 Another example: if I'm running through the forgot flow and I click on a link in an email that takes me to a URL, if the password manager has stored multiple sets of credentials for that realm, how does it find out which set to use to fill out the "old password"?
+=== issue 2: What is the "win" of each proposed change? ===
+For each change we're proposing, we should be clear about whether or not it actually will make password managers more reliable or useful, or whether it depends on other things happening as well. Can each change be adopted individually? Do any of them require other changes as well?
 == history ==