4 Commits

Author	SHA1	Message	Date
Bas van den Aakster	51fe405440	Unified Ed25519 authentication - remove peer_id/credentials system ... BREAKING CHANGE: Remove dual authentication system - Remove POST /register endpoint - no longer needed - Remove peer_id/secret credential-based auth - All authentication now uses username + Ed25519 signatures - Anonymous users can generate random usernames (anon-{timestamp}-{hex}) Database schema: - Rename peer_id → username in offers table - Rename answerer_peer_id → answerer_username in offers table - Rename peer_id → username in ice_candidates table - Remove secret column from offers table - Add FK constraints for username columns Storage layer: - Update D1 and SQLite implementations - All methods use username instead of peerId - Remove secret-related code Auth middleware: - Replace validateCredentials() with Ed25519 signature verification - Extract auth from request body (POST) or query params (GET) - Verify signature against username's public key - Validate message format and timestamp Crypto utilities: - Remove generatePeerId(), encryptPeerId(), decryptPeerId(), validateCredentials() - Add generateAnonymousUsername() - creates anon-{timestamp}-{random} - Add validateAuthMessage() - validates auth message format Config: - Remove authSecret from Config interface (no longer needed) All server endpoints updated to use getAuthenticatedUsername()	2025-12-10 22:06:45 +01:00
Bas van den Aakster	e3ede0033e	Fix UNIQUE constraint: Use (service_name, version, username) instead of service_fqn ... - Change UNIQUE constraint to composite key on separate columns - Move upsert logic into D1Storage.createService() for atomic operation - Delete existing service and its offers before inserting new one - Remove redundant delete logic from app.ts endpoint - Fixes 'UNIQUE constraint failed: services.service_fqn' error when republishing	2025-12-10 19:42:03 +01:00
Bas van den Aakster	9088abe305	Fix fresh schema to match D1 storage expectations ... Changed offers table to use service_id (nullable) instead of service_fqn. This matches the actual D1 storage implementation in d1.ts which expects: - service_id TEXT (optional link to service) - NOT service_fqn (that's only in the services table) Resolves 'NOT NULL constraint failed: offers.service_fqn' error.	2025-12-10 18:32:43 +01:00
Bas van den Aakster	00c5bbc501	Update database configuration and add fresh schema ... - Update wrangler.toml with new D1 database ID - Add fresh_schema.sql for clean database initialization - Applied schema to fresh D1 database - Server redeployed with correct database binding This resolves the 'table services has no column named service_name' error by ensuring the database has the correct v0.4.1+ schema.	2025-12-10 18:17:53 +01:00