LG-538 New Document Authentication Design

[stevegsa]

Why: So our users can verify their identity on mobile phones with a camera or desktop computers with a scanned image.

How: Detect whether a user is on a mobile phone or a laptop/desktop. Add new flows to accommodate desktop computers, mobile phones, desktop computers to mobile phones (ie user wants to use their phone camera because a desktop or laptop camera generally does not have enough resolution), and mobile phones to desktop computers (ie user has a scanner). Add image previews on document uploads. Supply different verbiage for taking a picture vs. uploading an image.

Hi! Before submitting your PR for review, and/or before merging it, please
go through the checklists below. These represent the more critical elements
of our code quality guidelines. The rest of the list can be found in
CONTRIBUTING.md

Controllers

• When adding a new controller that requires the user to be fully
  authenticated, make sure to add before_action :confirm_two_factor_authenticated
  as the first callback.

Database

• Unsafe migrations are implemented over several PRs and over several
  deploys to avoid production errors. The strong_migrations gem
  will warn you about unsafe migrations and has great step-by-step instructions
  for various scenarios.

• Indexes were added if necessary. This article provides a good overview
  of indexes in Rails.

• Verified that the changes don't affect other apps (such as the dashboard)

• When relevant, a rake task is created to populate the necessary DB columns
  in the various environments right before deploying, taking into account the users
  who might not have interacted with this column yet (such as users who have not
  set a password yet)

• Migrations against existing tables have been tested against a copy of the
  production database. See LG-228 Make migrations safer and more resilient #2127 for an example when a migration caused deployment
  issues. In that case, all the migration did was add a new column and an index to
  the Users table, which might seem innocuous.

Encryption

• The changes are compatible with data that was encrypted with the old code.

Routes

• GET requests are not vulnerable to CSRF attacks (i.e. they don't change
  state or result in destructive behavior).

Session

• When adding user data to the session, use the user_session helper
  instead of the session helper so the data does not persist beyond the user's
  session.

Testing

• Tests added for this feature/bug
• Prefer feature/integration specs over controller specs
• When adding code that reads data, write tests for nil values, empty strings,
  and invalid inputs.

[stevegsa]

Screenshots:

Desktop only flow:

---

User selects "Use your computer"

---

---

---

---

---

---

---

---

---

Mobile only flow:

---

User selects "Use your phone"

---

(user scrolls the screen)

---

---

---

---

---

---

---

---

---

Desktop to phone flow:

---

user selects "Use your phone"

---

---

---

text message:

---

Mobile to desktop flow:

---

User chooses "Use your computer"

---

---

Email message sent to desktop computer:

[jgsmith-usds]

This looks okay. We can polish in the next release if we need to.

[nickttng]

@stevegsa Latest iteration in InVision - DocAuth v5b if you want to peek. Meanwhile, I'm checking with @erinzstrenio about any content edit needed.

[stevegsa]

@nickttng the design looks great!

[nickttng]

@stevegsa We have reviewed and updated the v5b. It's good to go. Let us know if you have questions / thoughts.