Skip to content

LG-13663: recaptcha sign in failure page#10944

Merged
mdiarra3 merged 15 commits intomainfrom
LG-13663-recaptcha-sign-in-page
Jul 29, 2024
Merged

LG-13663: recaptcha sign in failure page#10944
mdiarra3 merged 15 commits intomainfrom
LG-13663-recaptcha-sign-in-page

Conversation

@mdiarra3
Copy link
Contributor

🎫 Ticket

Link to the relevant ticket:
LG-13663

🛠 Summary of changes

Adds page for users that fail sign in check.

📜 Testing Plan

  • User uses incognito or new browser or device
  • User attempts to log in,( for lower environment maek sure mock score is below threshold desired)(<0.3) by default.
  • User is redirected to sign in security page faiure after correctly signing in.
  • User is shown proper page that looks like below.

Screenshot

Screenshot 2024-07-16 at 11 11 26 AM
Screenshot 2024-07-16 at 11 39 06 AM
Screenshot 2024-07-16 at 11 39 12 AM
Screenshot 2024-07-16 at 11 39 15 AM

@mdiarra3 mdiarra3 requested a review from a team July 16, 2024 15:40
@mdiarra3
Copy link
Contributor Author

This will need to be in a holding pattern until the PR on identity-site page for this is made and merged in or else users will be taken to an error page in identity-site.

@aduth
Copy link
Contributor

aduth commented Jul 17, 2024

This will need to be in a holding pattern until the PR on identity-site page for this is made and merged in or else users will be taken to an error page in identity-site.

I think we'd planned to code this with the expected URL even if it doesn't exist today, since the feature isn't enabled for live users anyways.

@mdiarra3
Copy link
Contributor Author

This will need to be in a holding pattern until the PR on identity-site page for this is made and merged in or else users will be taken to an error page in identity-site.

I think we'd planned to code this with the expected URL even if it doesn't exist today, since the feature isn't enabled for live users anyways.

Oh good, Then ignore me,

@mdiarra3 mdiarra3 requested a review from aduth July 17, 2024 20:06
Copy link
Contributor

@aduth aduth left a comment

Choose a reason for hiding this comment

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

Couple minor comments, LGTM otherwise

Copy link
Contributor

@aduth aduth left a comment

Choose a reason for hiding this comment

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

LGTM

security_check_failed.contact: Contact %{app_name} support
security_check_failed.details: We don’t recognize the device or browser you’re signing in from.
security_check_failed.info_p1: 'Use the same device and browser you created your %{app_name} account with.'
security_check_failed.info_p2_html: Try <a href="%{piv_cac_url}">signing in with your government employee ID</a> if you are a government employee.
Copy link
Contributor

Choose a reason for hiding this comment

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

IMO I think it might be a little more reliable to get things through the i18n process to break the link title into its own key

Suggested change
security_check_failed.info_p2_html: Try <a href="%{piv_cac_url}">signing in with your government employee ID</a> if you are a government employee.
security_check_failed.info_p2_html: Try %{piv_cac_link_html} if you are a government employee.
security_check_failed.info_p2_link_html: signing in with your government employee ID

and then update the callsite to be like

    <li><%= t('security_check_failed.info_p2_html', piv_cac_link_html: link_to(t('security_check_failed.info_p2_link_html'), login_piv_cac_url) %></li> 

@mdiarra3 mdiarra3 merged commit bb5809b into main Jul 29, 2024
@mdiarra3 mdiarra3 deleted the LG-13663-recaptcha-sign-in-page branch July 29, 2024 13:09
mitchellhenke pushed a commit that referenced this pull request Jul 31, 2024
* changelog: Upcoming Features, Authentication, Recaptcha Sign in

* fix spec

* add test to ensure user redirected to security check failed

* add additional languges and page

* address comments

* lint fix

* address comments

* use c

* fix failed

* sign in security check controller spec added

* change spec name

* use back instead of cancel

* update security check failed spec
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.

3 participants