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

Fyst 1517 add ssn itin validation step to prior year access flow #5326

Open
wants to merge 62 commits into
base: main
Choose a base branch
from

Conversation

anisharamnani
Copy link
Contributor

@anisharamnani anisharamnani commented Jan 8, 2025

Link to pivotal/JIRA issue

Is PM acceptance required? (delete one)

  • Yes - don't merge until JIRA issue is accepted!

What was done?

  • Added ssn page verification
  • Added validations to check for existing archived intakes with matching ssn and email address
  • Added in the conditions for allowing access to the ssn page which includes checking in the session that the code was verified in the previous screen and checking that the request has not already been locked out

How to test?

  • Add units tests for the new form and controller
  • Updated verification code controller spec for adding condition to check if code was verified before accessing the identification number page
  • Added to the feature spec

Screenshots (for visual changes)

  • After
Screenshot 2025-01-17 at 2 31 01 PM

jnf and others added 29 commits December 27, 2024 12:01
… into FYST-1516-add-email-validation-step-to-prior-year-access-flow
* Add last year verification email

Co-authored-by: Em Barnard-Shao <[email protected]>
Co-authored-by: Hugo Melo <[email protected]>

* Rename previous year to archived intake

Co-authored-by: Hugo Melo <[email protected]>

* normalize

Co-authored-by: Hugo Melo <[email protected]>

---------

Co-authored-by: Em Barnard-Shao <[email protected]>
…il-validation-step-to-prior-year-access-flow
Copy link

github-actions bot commented Jan 8, 2025

Heroku app: https://gyr-review-app-5326-483eb329f5d0.herokuapp.com/
View logs: heroku logs --app gyr-review-app-5326 (optionally add --tail)

module StateFile
class CompletedReturnEmailAddressForm < QuestionsForm

end
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we have to delete this too.

@@ -0,0 +1,12 @@
module Navigation
class CompletedTaxReturnNavigation < Navigation::StateFileBaseQuestionNavigation
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we also must delete this.

@@ -0,0 +1,2 @@
<% content_for :page_title, t(".title") do %>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we delete this tooo.

@@ -0,0 +1,39 @@
# frozen_string_literal: true
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bye bye bye

@@ -92,7 +92,7 @@ def step_through_initial_authentication(contact_preference: :text_message)
expect(page).to have_text "Enter your email address"
fill_in I18n.t("state_file.questions.email_address.edit.email_address_label"), with: "[email protected]"
click_on "Send code"

save_and_open_page
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also this

@tahsinaislam tahsinaislam force-pushed the FYST-1517-add-ssn-itin-validation-step-to-prior-year-access-flow branch from 9ebf568 to b8dd33c Compare January 15, 2025 20:20
@anisharamnani anisharamnani force-pushed the FYST-1517-add-ssn-itin-validation-step-to-prior-year-access-flow branch from b8dd33c to 66ee195 Compare January 15, 2025 20:28
tahsinaislam and others added 21 commits January 15, 2025 14:37
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
…n-validation-step-to-prior-year-access-flow

Co-authored-by: Tahsina Islam <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Tahsina Islam <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
Co-authored-by: Anisha Ramnani <[email protected]>
@tahsinaislam tahsinaislam marked this pull request as ready for review January 17, 2025 22:39
Copy link
Contributor

@mrotondo mrotondo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One hunch of a potential bug in the interaction between this story and the previous one that I'd like you to check out, and one request for changes to comments, but looks good other than that! LMK when you've gotten a chance to check out the potential interaction with failed verification code attempts & I'll approve.

# need to change to address controller
else
create_state_file_access_log("incorrect_ssn_challenge")
current_request.increment_failed_attempts
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like we're re-using the same mechanism for marking "failed attempts" here as on the verification code page. If the user mis-enters a verification code and then gets it right on their second try, will that count against their total allowed failed attempts? In other words, should we reset failed attempts to zero after a user succeeds verification code authorization?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh I thought we did this in both controllers when the form is valid by line 17: current_request.reset_failed_attempts! but i could be wrong would be down to discuss on tuesday!

expect(intake_request.reload.failed_attempts).to eq(0)

expect(response).to redirect_to(root_path)
# need to change to address path
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you replace these comments with a TODO that reference the story ID where the work to change the path will be done?

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

Successfully merging this pull request may close these issues.

6 participants