Sign-in flow

A step of the Cloud application tree on Gradus, in the Frontend area: Second app, UI, browser tests.

The login, sign-up and sign-out screens, protected pages and a return to where the user was going, on whichever route you took. The shared access code goes.

Usually comes after: Choose how users sign in, any option of Sign-in.

Leads to: Your data is yours, Google sign-in, GitHub sign-in, Settings page.

Prompt for your AI assistant

Read the sign-in and frontend decision records in docs/decisions. Build what a user sees: login and sign-up pages, built in the frontend for own passwords or handed to the provider's page or components for a hosted provider, a sign-out control and a signed-in state in the header. Protect every page and endpoint of the first journey, on the server as well as in the UI, send a signed-out visitor to sign in and back to the page they wanted, accepting only paths on this site as the return address. Show clear messages for wrong credentials, an unverified address and an expired session. Remove the shared access code from the first deploy of the frontend. Add a browser test that signs up, signs out and signs in, walk the whole round trip once by hand on production and document in docs/ how to create a test user, making sure any shortcut for creating one is switched off in production.

This is https://gradus.kazet.blog/tree/cloud-application/step/sign-in-flow as plain HTML. In a browser the page also lets you mark the step forged and copy a message for your AI assistant.