Skip to main content
Jump to: navigation, search

Password Card Use Cases

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins logo 76Wx100H.jpg

Introduction

The following use cases are based on the "per account" metaphor design option (see [1]) but, with some mental gymnastics is also relevant to the "per role" and "per site" options.

First Visit

  1. User navigates their browser to a web page that includes a username / password login form, that has not been recorded in the past.
  2. User types a username / password
  3. User clicks the “login” button or equivalent.
  4. Higgins Password Manager pops-up a dialog: Do you want Higgins to remember this password?
    • Remember
    • Never for this site
    • Not Now
  5. User chooses one of the choices in the pop-up.
  6. Login form is submitted to web site as normal.

Subsequent Visit – Remembered Site

  1. User navigates their browser to a web page that includes a username / password login form, that has been previously “remembered”.
  2. When user clicks in username field, selector is triggered to open, displaying all password cards that are remembered for this site.
  3. User can select password card. After selecting card, User can also set “remember this card for this site”
  4. User clicks “send this card”
  5. Selector form-fills the username / password into the form and submits it, and logs its use in the selector. Alternatively, the user may need to click the “submit” button, after Higgins Password Manager fills the form.

Subsequent Visit – Remembered Site – Add Account

  1. User navigates their browser to a web page that includes a username / password login form, that has been previously “remembered”.
  2. User has more than one account at the site, so needs to create another Password Card for this site. Either:
    • They right-click in username field, which opens a browser menu, which includes an “Add Password Card” item. They select that choice.
    • When user clicks in username field, selector is triggered to open, displaying all password cards that are remembered for this site. They click “cancel” to close the selector.
  3. User enters username and password into form.
  4. User clicks “submit” or equivalent
  5. Pop-up informs the user that the username/password were stored on a new card.
  6. Login form is submitted to web site like normal.

Subsequent Visit – Remembered Site – Change Password

  1. User navigates their browser to a web page that includes a username / password login form, that has been previously “remembered”. Also, the user has (through another channel) changed their password on this site, such that the password remembered by Higgins is no longer valid.
  2. The password stored by Higgins is no longer valid, so the user does one of:
    • They right-click in username field, which opens a browser menu, which includes an “change Password ” item. They select that choice.
    • When user clicks in username field, selector is triggered to open, displaying all password cards that are remembered for this site. They click “cancel” to close the selector.
  3. User enters username and password into form.
  4. User clicks “submit” or equivalent
    • Pop-up informs the user that this is a different password than what is currently stored by Higgins for this site/username combination. They get the option to remember, or not now.
  5. Login form is submitted to web site like normal.

Subsequent Visit – “Never for this site”

  1. User navigates their browser to a web page that has previously been set to “never for this site”.
  2. Higgins Password Manager stays dormant – no pop-up or card selector.

Subsequent Visit – “Not Now”

  1. User navigates their browser to a web page that includes a username / password login form, that has been previously visited with a “not now” choice.
  2. Behavior is exactly the same as a never-visited site.

Managing Passwords

  1. User opens selector
  2. There is a new category of cards called “Password Cards”
  3. Any time a user has chosen “Remember” on a web page, a new password card is created, and is visible in the category.
  4. Clicking on a password card displays the card details in the selector, including the following (note that the password is not displayed since it is encrypted on the server, and is neither decryptable nor viewable in the selector):
    • Card Name: By default, the domain of the page where it was used. User Editable.
    • Card Image: user can upload a custom image to the card
  5. Site: The full URL of the page where it is used – not editable
    • Username: The captured username, displayed in clear text – not editable
    • Created: Date created – not editable
    • Last Use: Date last used, plus either “Success” or “Failure” – not editable
  6. Card Actions
    • Edit - user can edit certain fields
    • Delete – user can delete card
  7. Clicking on the Password Cards category displays a list view in the right-hand window, with two tabs:
    • Blocked – this lists all sites where the “never” command was used. It is here mainly to allow the user to un-block a site. It should have the following columns:
      • Site – the full URL of the site
      • Date – the date the site was blocked
      • Unblock – a control to un-block this site, removing it from the list.
    • Saved – this lists all the sites where a username / password has been saved. It is here to provide an overview across all the password cards. It should have the same columns as the detail view of the password card, plus “delete” for each card, which deletes the card, and “edit” which navigates to the edit screen for that card.

Back to the top