SSO/Forced Webview Value Add Research

[dumathane]

Description

As an app user, I want to access easy-to-use website content in a webview without having to sign on again.

As part of this story we want to:

• Identify which of the four potential URL locations are worth transforming into an in-app webview in order to enable SSO.

Acceptance Criteria

• Confirm all four of these links are behind login.

After reviewing the website locations and details, determine which should be enabled as a weblink SSO option in the app:

• NotificationSettingsScreen (va.gov/profile/notifications)
• NeedHelpData (va.gov/claim-or-appeal-status)
• NoAppointments/AppointmentCancelReschedule (va.gov/health-care/schedule-view-va-appointments)
• ApplyForVaHealthcare (va.gov/health-care/apply/application/introduction)

Accessibility Requirements

• AC 1
• AC 2
• AC 3

Notes & Open Questions

• Dependencies/Roadblocks:

  • Any internal/external dependencies?
  • Test accounts needed?

• Does this require QA?

• Dev Notes:

Ticket Checklist

• Acceptance criteria defined
• Labels added (front-end, back-end, feature)
• Linked to an Epic