Campaign Landing Page request: Legacy sign in credential migration

CarlDickerson commented 1 year ago

Description

As part of VA.gov's Campaign Landing Page, the CEDAR Identity Login.gov Adoption Team wants to launch a CLP to help provide updates on coming changes to how users sign in to VA. As VA transitions away from the use of DS Logon and My HealtheVet as valid sign in credentials for accessing VA websites and applications, this CLP would serve as resources to provide eduction around VA's new preferred credential--Login.gov, support on setting up a new account, and other information they may need to know surrounding the new secure sign in experience.

Intake

[x] What triggered this runbook? (Help desk ticket, Product team, Slack thread, etc) Trigger: CEDAR Identity Login.gov adoption product team
[x] Link to associated JIRA help desk ticket (if applicable) Help desk ticket: https://va-gov.atlassian.net/browse/VAHELP-5758
[x] Vanity URL requested: https://www.va.gov/secure_sign_in
[x] Name of submitter (if applicable) Submitter: Carl Dickerson

Acceptance criteria

Request comes in, via helpdesk request or direct to PO, or potentially in a Github issue.
[x] If not in a helpdesk request, redirect to Helpdesk or create a Helpdesk issue using email support@va-gov.atlassian.net or URL https://prod.cms.va.gov/help Helpdesk will use #sitewide-public-websites channel to request approvals
[x] In helpdesk ticket, @ mention Dave Conlon to review/approve the creation / existence / description of the CLP. Example text:

Hi Dave, Helpdesk has received a request for a new Campaign Landing Page. Can you confirm that this CLP is approved?

Approved

Helpdesk steps

[x] Helpdesk or any Drupal Admin can create the CLP node. Clone the CLP template node https://prod.cms.va.gov/initiatives/secure-sign-in
[x] If a new CMS editor user is needed, Helpdesk or any Drupal admin can create them and assign proper permissions according to CLP CMS account administration policy.
[x] Send the editor a link to the KB article: self-guided Campaign Landing Page training
[x] Notify #sitewide-public-websites team "New CLP requested and approved" with link to this Github issue for next steps.

Public Websites steps

[x] Create a Vanity URL redirect issue, IA must review & approve URL requests.

https://github.com/department-of-veterans-affairs/va.gov-team/issues/58142

[x] @mention Mikki Northuis in IA (#sitewide-content-ia) with link to Github issue, to provide Vanity URL request feedback. IA must review & approve URL requests.
[ ] When approved by IA, execute the steps of the URL change request ticket from step 2 above.
[ ] When redirect is verified in Production, close Redirect ticket as well as this ticket.

jilladams commented 1 year ago

Hi @CarlDickerson ! Thanks for the ticket. Could you follow the step in ticket to request the CLP creation from the Helpdesk team? They'll create the page, offer training if needed, get any users created in the CMS that might be necessary, and send you back to us after. (FYI @stefaniefgray )

redirect to Helpdesk or create a Helpdesk issue using email support@va-gov.atlassian.net or URL https://prod.cms.va.gov/help Helpdesk will use #sitewide-public-websites channel to request approvals

CarlDickerson commented 1 year ago

Hi @CarlDickerson ! Thanks for the ticket. Could you follow the step in ticket to request the CLP creation from the Helpdesk team? They'll create the page, offer training if needed, get any users created in the CMS that might be necessary, and send you back to us after. (FYI @stefaniefgray )

redirect to Helpdesk or create a Helpdesk issue using email support@va-gov.atlassian.net or URL https://prod.cms.va.gov/help Helpdesk will use #sitewide-public-websites channel to request approvals

@jilladams Helpdesk ticket was submitted last night, same time as Github request. VAHELP-5758 Campaign Landing Page request: Legacy sign in credential migration

For visibility @elizabethkochBT

stefaniefgray commented 1 year ago

Wrote to ask Dave C. if the request is approved, waiting on response

CarlDickerson commented 1 year ago

@stefaniefgray I see movement on this ticket, thank you. Once Dave C approves, is there a usual time frame that we can expect before we can start building out the CLP?

jilladams commented 1 year ago

Note: Dave's on PTO til Tues 5/9.

stefaniefgray commented 1 year ago

CLP created and KB article + draft template sent to editors earlier today in linked Jira ticket

mnorthuis commented 1 year ago

Hi all, because this is part of the broader comms of the identity work, please work with @DanielleThierryUSDSVA and Sitewide on this one. I'm going to put the vanity URL request on hold until this campaign content is more framed up and we can choose a vanity URL that reflects that messaging and the overall comms. We should have plenty of time to do that.

CarlDickerson commented 1 year ago

Hi all, because this is part of the broader comms of the identity work, please work with @DanielleThierryUSDSVA and Sitewide on this one. I'm going to put the vanity URL request on hold until this campaign content is more framed up and we can choose a vanity URL that reflects that messaging and the overall comms. We should have plenty of time to do that.

Thanks @mnorthuis Mikki, will do!

jilladams commented 1 year ago

Removed from PW sprints til we get the green light on redirect.

jilladams commented 11 months ago

@mnorthuis @DanielleThierryUSDSVA @CarlDickerson just scrubbing our backlog: Any updates here, or is this Legacy sign in creds migration CLP still blocked on greater identity work til we do the redirect?

DanielleThierryUSDSVA commented 11 months ago

Hi @jilladams. Thanks for checking in! I'm working on a broader communications and content strategy plan in coordination with Tom Black right now for sign-in changes. So go ahead and leave blocked for now until we have that settled. Thanks!.

jilladams commented 10 months ago

FYSA: @DanielleThierryUSDSVA we got a new ping on this CLP today via #16271 (duplicate ticket). I'm working on confirming with @TroyA6 / Helpdesk what they've heard from Carl Dickerson in JIRA, but meantime: let us know if any updates from your perspective, here. Thanks!

CarlDickerson commented 10 months ago

FYSA: @DanielleThierryUSDSVA we got a new ping on this CLP today via #16271 (duplicate ticket). I'm working on confirming with @TroyA6 / Helpdesk what they've heard from Carl Dickerson in JIRA, but meantime: let us know if any updates from your perspective, here. Thanks!

@jilladams I put in the request for a new CLP this morning. I wasn't sure if I should fill out the JIRA ticket yet until I got a confirmation, but I will go ahead and do that. I tried to annotate in the request that it was not duplicate per see. As our comms plan has changed, we're requesting a new CLP with a new URL. As we've been aligned, Danielle should be able to support/elaborate on this request.

jilladams commented 10 months ago

Ok. If someone can please advise re: the previous draft CLP as well, whether it will be "remodeled" to become the new CLP or should be archived, we can go from there. Thanks!

TroyA6 commented 10 months ago

@jilladams - I added this note to the other GH ticket as well, but this is all we received from Carl regarding this request: Components

Campaign Landing Page Where on the site is the issue occurring? (Please paste a direct link - thank you!)

https://www.va.gov/initiatives/sign-in-securely-with-logingov/ Description

Hi,

I am a member of VA OCTO Login.gov adoption team. We would like to request a new CLP to support our ongoing work to migrate Veterans to more secure sign-in credentials. This work is supported by Danielle Thierry and Dave Conlon (we have approvals on both ends).

Can you please CC replies to Lauren.Morris3@va.gov and Sophia.Philip@VA.gov.

DanielleThierryUSDSVA commented 10 months ago

Hi @jilladams. I was out on Friday so catching up on this ticket. Since the campaign has shifted away from being focused on Login.gov, we need a new CLP with a different URL. Dave and I chatted briefly and thought that creating a new one and redirecting the existing CLP's URL would be easier than reconfiguring the existing one. Let me know if that makes sense to you all or if you have any questions.

TroyA6 commented 10 months ago

@jilladams - Dave C commented that further approval is not needed, as this is coming from CAIA - documented in Slack

jilladams commented 10 months ago

Ok, thanks both. I'll reopen the new request, but need to clarify 2 things:

@DanielleThierryUSDSVA are we approved to archive the Draft node that was created for this ticket?
Sounds like I should reopen #16271. But: in that ticket body, the "NEW CLP node link" points to the existing CLP for this ticket that I'm requesting to archive. FYI @TroyA6. That means that we'll need a brand new cloned CLP -- I can handle that if Danielle confirms we're archiving the previous node.

jilladams commented 10 months ago

I'm wrong, just easily confused:

CLP created here for #13603 = https://prod.cms.va.gov/initiatives/secure-sign-in, published
CLP created for #16271 = https://prod.cms.va.gov/initiatives/migrating-veterans-accounts-to-more-secure-sign-in-credentials

Reopening 16271.

jilladams commented 10 months ago

Sorry, more questions:

Current published CLP = https://prod.cms.va.gov/initiatives/secure-sign-in
New CLP in draft = https://prod.cms.va.gov/initiatives/migrating-veterans-accounts-to-more-secure-sign-in-credentials

My questions:

@DanielleThierryUSDSVA in your note above, do I understand that you want to redirect the published CLP to the new CLP, when the new one gets published? Dave has previously suggested that CLPs should be time-limited, so I'm wondering if that factors into the redirect idea at all.
@CarlDickerson you filed #16275 on Friday as well, and I'm trying to understand how that connects or doesn't connect to these 2 CLP tickets. I added a note on that ticket for clarity as well -- feel free to answer there, just flagging here for everyone's awareness.

CarlDickerson commented 10 months ago

@jilladams I answered in #16275 but I will also answer here for continuity. #16275 is a duplicate request of #16271. Not realizing that my HelpDesk request would trigger a Github issue, I also went and created ticket for this work myself. So I think that #16275 can be closed since the work is being tracked elsewhere.

jilladams commented 10 months ago

Thanks very much. Now that we have that cleared up, I'll use #16271 for any remaining questions. The CLP that was created via this ticket (13603) has been published (9/25/23), so I'm closing this ticket as well.

department-of-veterans-affairs / va.gov-cms