Closed Bug 797947 Opened 12 years ago Closed 12 years ago

Reset PIN userflows

Categories

(Marketplace Graveyard :: Consumer Pages, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: krupa.mozbugs, Assigned: msandberg)

References

Details

(Keywords: uiwanted, Whiteboard: [ux input wanted])

We need a way for users to be able to reset their PIN. We need to figure out the flows for two usecases-

a) The user remembers their old PIN and just wants to reset 
b) The user doesn't remember their old PIN and needs to test.
Blocks: 795105
Assignee: nobody → msandberg
blocking-basecamp: --- → +
Keywords: uiwanted
Priority: -- → P2
We discussed this in a meeting today. Before allowing a pin reset we will call id.logout() and id.request() to log the user out and back in again. These methods exist but we are waiting on additional behavior of id.logout().
The reset will begin with:

  navigator.id.logout({everywhere: true});
  navigator.id.request(...);

The everywhere option is something new that the Identity team will add for us.
The flow for these cases will be the same. 

- the enter pin screen has two buttons, "next" and "forgot pin?"
- "forgot pin" will prompt the user to enter a new pin.
- after entering a new pin the user will be asked to confirm it. The confirm new pin screen will inform the user they have to sign in to complete the reset. Two buttons available: "sign in" (starts sign in flow) and "cancel" (returns to where the purchase was initiated from - pin is not reset). 

See pages 19, 22-23 in updated specs:
https://www.dropbox.com/s/fjr5aqt8mqq8faq/marketplace-id-payments-20121017.pdf
Ok so backend changes needed for this: 

* We'll need a place to store the new PIN until it is verified. 
** We'll need a time when that happened so we can dump it after X minutes. 
* Login will check the new PIN if it exists and is not expired otherwise it checks the old pin.
* If user hits cancel, we'll need to POST or something to webpay to tell it to clear the new PIN so only the old PIN exists.

This seem sane?
(In reply to Wraithan from comment #4)

> * Login will check the new PIN if it exists and is not expired otherwise it
> checks the old pin.
I don't understand this one.  Otherwise they look fine.  Maria's link is a 500 for me right now so can't confirm.
Hm, let's do this instead - Dropbox links seem very unreliable. 

See UX detailed specs linked from https://wiki.mozilla.org/Apps/ID_and_Payments
- Payment - enter pin (currently page 19)
- Payment - reset pin (currently page 22)
- Payment - reset pin (currently page 23)
Not on-device - removing nom.
blocking-basecamp: + → ---
The UX for this is done. See Maria's links above. Wraithan is implementing the flows in bug 802646
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.