Nicolas
bbd9afe8aa
L'admin etait une 2e app front Vite independante (apps/admin-web, port 5174,
Dockerfile nginx, service compose dedie, job CI propre) non demandee. Toute
l'UI passe dans apps/web sous le prefixe /admin ; seul le frontend est
fusionne, l'authentification admin reste entierement separee.
Front (apps/web/src) :
- pages -> pages/admin/{login,dashboard,monitoring,corrections,catalog}/,
layout -> layouts/AdminLayout.tsx, contexte + garde -> features/admin/.
- client API -> api/admin-client.ts : classe AdminApiError (evite la
collision avec ApiError), lit VITE_API_URL (plus de VITE_ADMIN_API_URL).
- routes /admin/* dans App.tsx, enveloppees d'AdminAuthProvider +
RequireAdmin -> le probe GET /admin/auth/me ne tourne que sous /admin.
- reutilise l'i18n, lib/zod-errors, services/error-message.service et le
theme SCSS de apps/web ; bloc i18n admin.* fusionne dans la locale fr
(les cles errors etaient deja toutes presentes).
- corrige une race dans CatalogPage (reponse d'un onglet precedent qui
ecrasait l'onglet courant, exposee par le double-mount StrictMode) via
un ref requestSeq.
Auth admin inchangee : table AdminUser, cookie admin_session,
ADMIN_JWT_SECRET, script create-admin.ts.
Infra :
- docker-compose : service admin-web + ADMIN_WEB_PORT supprimes (l'app
`app` sert deja le front construit).
- ADMIN_CORS_ORIGIN retire (meme origine) : env.ts, app.ts, .env.example.
- job CI "Run admin-web E2E tests" supprime ; les specs admin-* tournent
dans le job web (apps/web/cypress/e2e/admin-*.{cy.ts,feature}).
- apps/api/.env.example : ajout ADMIN_JWT_SECRET / ADMIN_INITIAL_*.
- recharts ajoute a apps/web ; pnpm-lock regenere.
- specs/backend-architecture.md : section admin mise a jour.
Verifie : biome + tsc -b (web/api) + pnpm -r build verts ; Cypress web
102/103 (l'unique echec est le flake pre-existant recipe-form.feature
"Preloads ..." de clipping headless, sans rapport) ; 16/16 specs admin ;
45/45 composants.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
24 lines
1 KiB
Gherkin
24 lines
1 KiB
Gherkin
Feature: Admin login
|
|
As an operator
|
|
I want to sign in to the admin application
|
|
So that I can reach the metrics, monitoring and correction-triage sections
|
|
|
|
Scenario: A wrong password shows a translated error, no redirect
|
|
Given the admin session check returns unauthenticated
|
|
And admin login fails with invalid credentials
|
|
When I visit "/admin/login"
|
|
And I fill in the "email" field with "ops@example.com"
|
|
And I fill in the "password" field with "wrong"
|
|
And I click the button "Se connecter"
|
|
Then I should see "Email ou mot de passe incorrect"
|
|
And the URL should include "/admin/login"
|
|
|
|
Scenario: A correct login lands on the dashboard
|
|
Given the admin session check returns unauthenticated
|
|
And admin login succeeds as "Ops"
|
|
When I visit "/admin/login"
|
|
And I fill in the "email" field with "ops@example.com"
|
|
And I fill in the "password" field with "correct-horse"
|
|
And I click the button "Se connecter"
|
|
Then the URL should not include "/admin/login"
|
|
And I should see the heading "Tableau de bord"
|