This is the UI shown when clicking forgot pin. It's distinct from the actual pin resetting steps. On clicking cancel the user should return to enter-pin assuming it's relevant. On clicking continue the user should be put through the following flow: * Logout from persona and provider * Login successfully * Then they can start the reset pin flow proper. It's likely this will need an API flag similar to the ones for the locked status to inform the UI when to show the necessary forms.

The 'reset-start' page is complete. The remaining tasks here are implementing the client-side bits in Spartacus to handle the actual reset. e.g. Logging out of Persona/Webpay/Provider (Bango requires this not Boku) Re-authentication via persona. And after successful re-auth -> reset-pin. The actual reset-pin views are done so except minor tweaks this should mostly be about the logout + re-auth.

Note: bug 851676 is a condition of satisfaction of this implementation.

PR: https://github.com/mozilla/spartacus/pull/57

PT1 is in https://github.com/mozilla/spartacus/commit/2a4b91c41eb952d3d799a0efb3b1dc4e2bf1a61a next step (in progress) is locally validating the reset flow and any tweaks + some flow docs for in-depth how it happens to aid validation.

As discovered at the tail-end of last-week. navigator.id.request must be called from a click or it doesn't work correctly. Raised bug 1026593 to track it.