Difference between revisions of "Wallet User Experience"

From MgmtWiki
Jump to: navigation, search
(Goals)
(Goals)
Line 10: Line 10:
 
==Goals==
 
==Goals==
 
The following are the required success criteria for both the user and the RP in establishing and maintaining an enduring relationship. Wallets supporting ephemeral connection are possible and may be addressed in a subsequent list as needed.
 
The following are the required success criteria for both the user and the RP in establishing and maintaining an enduring relationship. Wallets supporting ephemeral connection are possible and may be addressed in a subsequent list as needed.
# RPs will have the means to know if the meet the criteria for giving users control of their own identifiers.
+
# RPs will have the means to know if they meet the criteria for giving users control of their own identifiers.
 
# A user of common capability will be able to  
 
# A user of common capability will be able to  
install one or more wallets and created zero or more identifiers on each wallet.
+
install one or more wallets and create zero or more identifiers on each wallet.
 
# The user can add or remove wallets at any time.
 
# The user can add or remove wallets at any time.
 
# The RP can display for the user's selection on the user's browser a small number of choices that are created entirely by browser code and information from the DOM provided by the user's browser.
 
# The RP can display for the user's selection on the user's browser a small number of choices that are created entirely by browser code and information from the DOM provided by the user's browser.

Revision as of 02:33, 3 March 2021

Full Title

The User Experience of get a user to selection the correct piece of mobile code as a user agent for a particular Relying Party on the user's identifier.

Context

  • The context is giving user's control over the identifiers that they use
  • The primary context is the user's mobile smartphone. A secondary context is the user on a laptop computer connected to the internet.
  • The operating assumption is that the user has contacted the RP with a browser and that the identity security code is a separate native or web application that will be referred to below as the Wallet.
  • For convenience of this list a wallet can include references other wallets.

Goals

The following are the required success criteria for both the user and the RP in establishing and maintaining an enduring relationship. Wallets supporting ephemeral connection are possible and may be addressed in a subsequent list as needed.

  1. RPs will have the means to know if they meet the criteria for giving users control of their own identifiers.
  2. A user of common capability will be able to

install one or more wallets and create zero or more identifiers on each wallet.

  1. The user can add or remove wallets at any time.
  2. The RP can display for the user's selection on the user's browser a small number of choices that are created entirely by browser code and information from the DOM provided by the user's browser.
  3. Upon selection of one of those options, the user will be able to access a wallet previously provisioned with an identifier or a wallet with a list of other wallets.
  4. The user will have full and effective control of the selection of an identifier that meets the RP criteria.
  5. If such a identifier does not exist, the user be given simple and effective instructions on creating such a key that does meet the criteria.

References