Enable other sites to fully use the VA.gov header/footer/login stack

[davidsbao]

Story or Description

As part of the broader Web Brand Consolidation effort, one of the core tenets is to simplify the login experience across VA's various websites.

The current login landscape of the main web properties is as follows:

• eBenefits
  • Credentials
    • DS Logon
  • ID Broker/Backend
    • SSOe
• My HealtheVet
  • Credentials
    • MHV
    • DS Logon
    • ID.me
  • ID Broker/Backend
    • MHV Credential: MHV homegrown
    • DS Logon/ID.me Credential: SSOe
• VA.gov
  • Credentials
    • MHV
    • DS Logon
    • ID.me
  • ID Broker/Backend
    • ID.me + VA.gov homegrown

As VA.gov is the single front door to the agency, the current VA.gov login stack needs to be usable by both eBenefits and MHV, even if they maintain separate tech stacks for the rest of their sites' implementation. By extension, this means that other properties may also use the full VA.gov header and footer to further help bring them in accordance with VA.gov

Acceptance Criteria

• [ ] eBenefits can replace their login module with VA.gov's
• [ ] My HealtheVet can replace their login module with VA.gov's
• [ ] SSO between eBenefits, MHV, VA.gov, and any other property (e.g. future Cerner) is multidirectional

Def of Done

• [ ] Issue is connected to Epic
• [ ] All AC met

[annaswims]

ssoe documentation lives at https://vaww.oed.portal.va.gov/sites/vrm/IAM/playbooks/Pages/SSOe/SSOe.aspx