Auth and sessions
The problem
A home equity operation goes through many hands (partner, analysis, legal, payment) and every stage requires documents and checks. Without a single place, operations stalled and nobody knew which stage they were in or what was missing to move on.
auth is the identity every other service trusts: users, organizations, teams, permissions, MFA and sessions. It signs tokens with RS256 and the others verify with the public key. Run the scenarios to see sign-in with MFA, rotating refresh and what happens when a stolen token is used.
Decisions and why
- One session per app
- Each front-end has its own cookie and session; signing out of one does not affect the others.
- Reuse revokes everything
- An already rotated token showing up again means theft: every session is revoked and audited.
- Suspension ends sessions in the same transaction
- The person is out as soon as the 15-minute access token lapses.
requestresponse
Pick a scenario above to watch the message travel through the architecture.
What it looks like
Replica of the pipeline board with fictional data (internal system) esteira.evilrabbit.com.br/lines/triage
Triagem
Conferência de dados2
Marina SouzaGMR$ 480 mil 1 d
Paulo HenriqueR$ 1,2 mi hoje
Combate à fraude1
Ricardo AlvesAPR$ 750 mil 4 d
Validação dos documentos2
Carla PradoGMR$ 610 mil 2 6 d
João ReisR$ 295 mil 2 d
Aguardando aprovação0
Nada aqui