fix(c4): sequence diagram — username → email in auth flow

Three stale references: "Enter username + password", Base64 encode
"user:password", and SELECT WHERE username — all updated to email to
match AppUserRepository.findByEmail() and CustomUserDetailsService.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Marcel
2026-05-06 12:53:32 +02:00
parent af24d63176
commit caf86b3225

View File

@@ -517,12 +517,12 @@ sequenceDiagram
participant Backend as Backend (Spring Boot) participant Backend as Backend (Spring Boot)
participant DB as PostgreSQL participant DB as PostgreSQL
User->>Browser: Enter username + password User->>Browser: Enter email + password
Browser->>Frontend: POST /login (form action) Browser->>Frontend: POST /login (form action)
Frontend->>Frontend: Base64 encode "user:password" Frontend->>Frontend: Base64 encode "email:password"
Frontend->>Backend: GET /api/users/me<br/>Authorization: Basic <token> Frontend->>Backend: GET /api/users/me<br/>Authorization: Basic <token>
Backend->>Backend: Spring Security parses Basic Auth Backend->>Backend: Spring Security parses Basic Auth
Backend->>DB: SELECT user WHERE username=? Backend->>DB: SELECT user WHERE email=?
DB-->>Backend: AppUser + groups + permissions DB-->>Backend: AppUser + groups + permissions
Backend->>Backend: BCrypt.matches(password, hash) Backend->>Backend: BCrypt.matches(password, hash)
Backend-->>Frontend: 200 OK — UserDTO Backend-->>Frontend: 200 OK — UserDTO