Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI: Backup Codes setup #39

Closed
iandunn opened this issue Jan 11, 2023 · 3 comments
Closed

UI: Backup Codes setup #39

iandunn opened this issue Jan 11, 2023 · 3 comments
Assignees
Milestone

Comments

@iandunn
Copy link
Member

iandunn commented Jan 11, 2023

We need to add a UI for setting up Backup Codes for the first time. The TOTP screen will redirect to this screen after the user has setup TOTP.

WordPress/two-factor#504 will need to be used locally until it's merged, so that we can use the REST API to interact with the upstream plugin.

See #18 for mockups, may also need to look at WordPress.com for some of the interactions that aren't covered in the screenshots.

This could potentially be done in two PRs, ala Thinking in React: one to stub out the UI, and then a second to add dynamic functionality.

@iandunn iandunn added this to the MVP milestone Jan 11, 2023
@iandunn
Copy link
Member Author

iandunn commented Jan 18, 2023

There are some minor changes to backup-codes.js in #36 that haven't been merged to trunk yet. If anyone picks this up before they are, it'd be good to cherry pick them before starting, to avoid merge conflicts.

@iandunn
Copy link
Member Author

iandunn commented Jan 20, 2023

To reduce the scope for the MVP, we could skip the copy/print/download buttons, and so we only display the codes. The user could manually do those actions for now.

If we go that route, we should open a new issue for Iteration 1 where we add them.

@iandunn
Copy link
Member Author

iandunn commented Jan 25, 2023

Refined the UI stubs in 4be26e2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant