-
Notifications
You must be signed in to change notification settings - Fork 166
LG-14552: Ensure users can't reach the IPP verify info controller without a threatmetrix session id #11858
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
LG-14552: Ensure users can't reach the IPP verify info controller without a threatmetrix session id #11858
Changes from all commits
24a2d7f
f138002
df69395
6747149
6cf0892
4974d87
406cd00
2b4aa47
6713398
1c6ecaf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,12 +14,11 @@ | |
| allow(IdentityConfig.store).to receive(:usps_ipp_transliteration_enabled) | ||
| .and_return(true) | ||
| stub_sign_in(user) | ||
| stub_up_to(:hybrid_handoff, idv_session: subject.idv_session) | ||
| stub_up_to(:ipp_state_id, idv_session: subject.idv_session) | ||
| allow(user).to receive(:establishing_in_person_enrollment).and_return(enrollment) | ||
| subject.user_session['idv/in_person'] = { | ||
| pii_from_user: pii_from_user, | ||
| } | ||
| subject.idv_session.ssn = nil | ||
| stub_analytics | ||
| end | ||
|
|
||
|
|
@@ -97,17 +96,6 @@ | |
| expect(response).to render_template :show | ||
| end | ||
|
|
||
| context 'when address1 present' do | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Since the flow policy stipulates that we should rely on the @jennyverdeyen I'd be curious to hear any thoughts you have on this!
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This makes sense! Since we know this was a duplicate check for the redirect behavior that was already being handled in the state id controller, I went to see if there were tests for this in the state id controller specs. I think there maybe aren't... Is this something we should add there?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @jennyverdeyen Good point! I added a new test to the address_controller_spec in 2b4aa47. Let me know if that provides enough coverage or if you want me to add another test. |
||
| before do | ||
| subject.user_session['idv/in_person'][:pii_from_user][:address1] = '123 Main St' | ||
| end | ||
| it 'redirects to ssn page' do | ||
| get :show | ||
|
|
||
| expect(response).to redirect_to idv_in_person_ssn_url | ||
| end | ||
| end | ||
|
|
||
| it 'logs idv_in_person_proofing_address_visited' do | ||
| get :show | ||
|
|
||
|
|
@@ -170,6 +158,12 @@ | |
| ) | ||
| end | ||
|
|
||
| it 'enables the user to navigate to the ssn page after entering their residential address' do | ||
| put :update, params: params | ||
|
|
||
| expect(response).to redirect_to(idv_in_person_ssn_url) | ||
| end | ||
|
|
||
| it 'logs idv_in_person_proofing_address_submitted with 5-digit zipcode' do | ||
| put :update, params: params | ||
|
|
||
|
|
@@ -178,6 +172,7 @@ | |
|
|
||
| context 'when updating the residential address' do | ||
| before do | ||
| stub_up_to(:ipp_verify_info, idv_session: subject.idv_session) | ||
| subject.user_session['idv/in_person'][:pii_from_user][:address1] = | ||
| '123 New Residential Ave' | ||
| end | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed
confirm_in_person_address_step_neededin order to conform with the flow policy documentation.