[Eng] Sign in page

[racheledelman]

Overview

As a builder, I would like to sign in, so that I can access the Forms Platform.

Banner:

Just looking for a form?
This account is for government employees who are creating and managing forms. If you are a member of the public trying to fill out a form, you do not need to sign into this website. If you cannot access a form, contact the person or agency who sent you the link.

Sign in:

Sign in to your account
You can access your Forms Platform account by signing in with Okta.

Context

This is part of user flow for the Builder Homepage #478. DOJ users will be logging in with Okta.

Acceptance Criteria

Required outcomes of the story

• Sign in / Sign out link is added to header
• A sign in page is created using UWDS's sign in template
• Sign in page appears whenever a user attempts to access a page that is only accessible while signed in (everything but the splash page?)
• There is a banner on the sign in page for any lost members of the public

Research Questions

• Does Okta handle sign in errors, or do we need to design something for that?

Tasks

Research, design, and engineering work needed to complete the story.

• [ ]

Definition of done

The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.

• Behavior
  • Acceptance criteria met
  • Implementation matches design decisions
• Documentation
  • ADRs (/documents/adr folder)
  • Relevant README.md(s)
• Code quality
  • Code refactored for clarity and no design/technical debt
  • Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed
  • Code is reviewed by team member
  • Code quality checks passed
• Security and privacy
  • Automated security and privacy gates passed
• Testing tasks completed
  • Automated tests pass
  • Unit test coverage of our code >= 90%
• Build and deploy
  • Build process updated
  • API(s) are versioned
  • Feature toggles created and/or deleted. Document the feature toggle
  • Source code is merged to the main branch

Decisions

• Optional: Any decisions we've made while working on this story