The full authorization-code login flow between a user, SPA, auth server, user database and resource API.
This sequence diagram walks through an OAuth 2.0 authorization-code login: the user clicks log in, the SPA redirects to the auth server, credentials are verified against the user database, an auth code is exchanged for access and refresh tokens, and the API is finally called with a bearer token.
Eleven ordered messages across five participants — all generated from one sentence and ordered correctly. Ridvay turns a description of an interaction into a clean, editable sequence diagram: add a step, rename a message, or export it for your API docs.
“Sequence diagram for an OAuth 2.0 authorization-code login between a User, a single-page web app, an auth server, a user database and a resource API.”
Describe it in plain English — Ridvay builds and lays it out. Free to start.
Open the editor