feat: Provisionner automatiquement un nouvel établissement
Some checks failed
CI / Backend Tests (push) Has been cancelled
CI / Frontend Tests (push) Has been cancelled
CI / E2E Tests (push) Has been cancelled
CI / Naming Conventions (push) Has been cancelled
CI / Build Check (push) Has been cancelled

Lorsqu'un super-admin crée un établissement via l'interface, le système
doit automatiquement créer la base tenant, exécuter les migrations,
créer le premier utilisateur admin et envoyer l'invitation — le tout
de manière asynchrone pour ne pas bloquer la réponse HTTP.

Ce mécanisme rend chaque établissement opérationnel dès sa création
sans intervention manuelle sur l'infrastructure.
This commit is contained in:
2026-04-08 13:55:41 +02:00
parent bec211ebf0
commit e72867932d
107 changed files with 9709 additions and 383 deletions

View File

@@ -36,11 +36,9 @@ final class PasswordResetEndpointsTest extends ApiTestCase
// Should NOT return 401 Unauthorized
// It should return 200 (success) or 429 (rate limited), but never 401
self::assertNotEquals(401, $response->getStatusCode(), 'Password forgot endpoint should be accessible without JWT');
// The endpoint always returns success to prevent email enumeration
// Even for non-existent emails
self::assertResponseIsSuccessful();
$status = $response->getStatusCode();
self::assertNotEquals(401, $status, 'Password forgot endpoint should be accessible without JWT');
self::assertContains($status, [200, 201, 429], 'Expected 200/201 (success) or 429 (rate limited)');
}
#[Test]