Skip to main content

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.

Jump to: navigation, search

Qt Selector Account UI

Revision as of 07:37, 27 October 2009 by Unnamed Poltroon (Talk) (Added note on PBKDF2)

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Higgins logo 76Wx100H.jpg

This page is to contain mockups and description of the Account Selector UI.

Background

The selector can optionally connect to an external Authentication Service 1.1 for the purpose of gaining access tokens that it can use to access other selector supporting services such as the Attribute Service 1.1, CardSynce Service 1.1.

Case 1: User does not have account at authentication service:

  • Clicking Login Now switches to Case 2.
  • After Step 1, server sends the OTP password for serialized selector.
  • Continue without authorization code creates the account in the "non-serialized" mode (does not require enrollment of selectors).
  • Passphrase is used to locally create an encryption key, for instance by means of PBKDF2. It is not sent to the Auth service. Alternatively, if the Password is not know to the auth service (i.e., only proof of it is known), then the Password can be used to locally create an encryption key, and the Passphrase is not necessary.

New-account-step1.png

  • Authorization Code is the OTP sent to the user
  • Device Name is a user-chosen name for this device. It would be nice to allow spaces in the names. Device Name must be unique for the user account.

New-account-step2.png


Case 2: User has account at auth service.

  • Clicking Sign up for Account switches to Case 1.
  • Clicking forgot password? initiates the password reset flow.
  • If the selector was downloaded directly from a logged-in session at the Auth service, the Username field would be pre-filled. The password would still need to be entered.


Authorize-step1.png

  • In this case, if the account is already "serialized", they get the Step 2 screen, below.
  • If the account is not "serialized" then there is no step 2 - they just are connected.

Authorize-step2.png

Case 3: Selector previously configured

  • If the device is not logged-in, but it does have one or more saved usernames, this should be the screen that is first shown to the user.
  • Username is a pick list of all usernames that are authorized and "remembered" on this device.
  • Clicking Add another username switches to Case 2.
  • Clicking forgot password? initiates the password reset flow.

Login.png

Case 4: Forgot Password

  • Clicking Sign up for Azigo(or Higgins, in this case - oops!) switches to Case 1.
  • Upon clicking Next, the server sends an OTP to the all the registered contact points (just email for now, but in the future it could include SMS, phone, etc.).

Forgot-password.png

Forgot-password-2.png

Case 5: Manage Selectors

  • This is from a logged-in session in the selector.

Accounts-menu.png 

  • The My Devices tab shows a list of devices that are authorized to connect to the account.
  • Device Name is what the user entered in Step 2 of Case 1 or  Case 2.


Accounts-devices.png

  • If the account is not "serialized", then this screen is shown for the My Devices tab.

Accounts-devices-disabled.png

  • While the initial account setup collects one email address, this screen allows the user to add/remove additional email addresses. It could be expanded to support other contact points (SMS, voice phone, etc. in the future)

Accounts-settings.png

See Also

Back to the top