Supporting third-party authentication

[gopixelsgo]

Description

This is a placeholder to discuss as a team what it means to include this in our scope. Recent PO feedback has clarified this as a requirement. Our current scope has kept the focus on Veteran and Beneficiary respondents. Implementing the respondent pattern and aligning with the greater VA experience means supporting 3rd party (VSO, PoA) authentication.

For example, the prompt in the 'Who will submit this form?' step, would ask:

Who is allowed to submit this form? [ ] Allow a third party to sign and submit this form for a Veteran or Beneficiary(ies) [ ] Only the Veteran or Beneficiary can sign and submit this form

If the first option is chosen we’ll need to include login and credential upload.

Impacts to UX: Intro copy communicating the need to have the credential first, collecting their name and info (assuming they are the signor - also is that automatic?), offering a link to that form, etc.

Tasks

• [ ] Review and discuss as a team
• [ ] Identify next steps

Acceptance Criteria

• [ ] Next steps identified
• [ ] New ticket(s) and applicable epic created as needed

[Karak888]

kara to create this as an epic. will need discussion in order to know what next steps will be from UX as well as engineering.

[brian-wilke]

Moving this back to current sprint to be pointed so it can be In Progress for this sprint. Suggest we point items before they are included in a sprint plan for the future. Will include this in retro for Sprint 11.

[Karak888]

I am taking this off of you all of course unless you have tickets to add. I am closing this as I have already created an epic for this in GH and we can create tasks and subtasks under epic as we go through. I am taking the lead on this as discussed.

[Karak888]

This is not at an epic level and will move this to become a task rather than an epic. Can always re-assess at a later date. @gopixelsgo @brian-wilke