Closed wesrowe closed 3 weeks ago
@sterkenburgsara – FYSA, I added a link to your "Verify" Figma file in the main ticket body above. Please update this ticket when content and CTA link destination are known for the MHV credential.
Designs are still in flight (CAIA), and no clear timeline to resolution. NOT taking into Sprint 27 at this time.
Per slack thread on 3/19, CAIA still noodling.
slack thread from recent days about the possible (but unlikely) need for a version of this alert where the sign-in service is not specified.
@sterkenburgsara, I would appreciate your pinging CAIA when you have a chance. And please link the relevant CAIA ticket on this one.
Note: identity team has updated the acronyms that they use to refer to identity verification levels. LOA1 is now IAL1 and LOA3 is now IAL2.
Per Sara, this ticket is blocked by a new need to revise the content. Removing it from Sprint 32, hope for new content by S33.
Per this thread from last sprint, we were asked to hold on implementing this alert until a technical step (that a shadow ID.me account is created for MHV basic users when they log in using their MHV credential on VA.gov) mentioned in the alert content can be validated with Carnetta Scruggs and Joe Niquette.
Myself, Patrick, Laura W., and Danielle Thierry synced on 6/25/2024 to discuss and the following were determined as next steps:
Carnetta's response to Patrick's email is the bolded terminology in the image below (see words: nope, maybe, something else) - this response is not clear to me. Laura and I are hoping that Patrick will follow-up and we will wait until they figure this out before editing content.
@jzucadi sorry for late-changes, but I synced with @jonathanjnelson and @carlosfelix2 yesterday about standardizing things we're exposing for various alerts. In that call, it was decided that lots of things I originally put in the Figma file for this alert should not display for this scenario, where the user is not signed in with an ID-verified account. I also commented on the PR & will update Figma asap.
This work is blocked due to more UX changes being decided on, details in this thread: https://dsva.slack.com/archives/C0581MN69TJ/p1722261242087759?thread_ts=1722260409.416559&cid=C0581MN69TJ
@jzucadi Please see updated content in Figma here
Environment: Staging, Production
In staging, the MHV account login doesn't work so I created a MHV basic account in production to test this alert. Verified that the alert appears for my prod account. In staging, verified that this alert doesn't appear for id.me login types
Are links destinations being checked/ verified as part of QA process? If not can I do a check on alerts too?
On Thu, Aug 15, 2024 at 13:53 Allan To @.***> wrote:
Environment: Staging, Production
In staging, the MHV account login doesn't work so I created a MHV basic account in production to test this alert. Verified that the alert appears for my prod account. In staging, verified that this alert doesn't appear for id.me login types Screenshot.2024-08-15.at.10.24.46.AM.png (view on web) https://github.com/user-attachments/assets/85d91e5f-e28b-48a5-8e4b-355b39643241
— Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-team/issues/77357#issuecomment-2291991236, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3NULPHHDPKESKSMPVIZ2MLZRT2LRAVCNFSM6AAAAABD66VSYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJRHE4TCMRTGY . You are receiving this because you were mentioned.Message ID: @.*** .com>
Yes they are!
Yay, go team! Thanks for confirming.
On Thu, Aug 15, 2024 at 16:45 Allan To @.***> wrote:
Yes they are!
— Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-team/issues/77357#issuecomment-2292324828, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3NULPDDLLC7LPKWOBQFVQ3ZRUORPAVCNFSM6AAAAABD66VSYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJSGMZDIOBSHA . You are receiving this because you were mentioned.Message ID: @.*** .com>
Description
User story
As a Veteran signed-in using a non-LOA3 My HealtheVet basic credential, I want to see a contextual alert that tells me I cannot use this sign-in credential. I want to clearly be told what to do next isntead: create a new Login.gov or ID.me account, verify it, and register with My HealtheVet. This will help me understand why I can't see the My HealtheVet on VA.gov tools and have clear instructions for getting unstuck.
Background
Notes:
Screen shot
Alert content:
H2
You need to sign in with a different account to access My HealtheVetbody text
To protect your health information and prevent fraud and identity theft, we can only give you access when you sign in with a verified account. You have 2 options: a verified Login.gov or a verified ID.me account.If you already have a Login.gov or ID.me account, sign out of VA.gov. Then sign back in using that account. We’ll tell you if you need to verify your identity or take any other steps.
If you want to create a Login.gov account, follow these steps:
If you want to create an ID.me account, you should know that we started this process for you when you signed in to VA.gov. Follow these steps to finish creating your account:
button
[button] Sign outlink
[link] Learn more about how to access My HealtheVet on VA.govTasks
Acceptance criteria