Feat: auth middleware

migrations/0002_create-profile.sql

@@ -60,21 +60,6 @@ CREATE TABLE IF NOT EXISTS profile (
 	PRIMARY KEY (id)
 );
 
-DROP TABLE IF EXISTS passwords;
-
-CREATE TABLE IF NOT EXISTS passwords (
-	-- The UUID of the profile this link belongs to
-	id TEXT NOT NULL UNIQUE COLLATE BINARY,
-	-- Schema version to use
-	-- Here it is useful if we update the password encryption algorithm in the future
-	schemaVersion INTEGER NOT NULL DEFAULT 1,
-	-- The person's account password
-	-- This should be propperly hashed and salted!
-	password TEXT NOT NULL,
-
-	FOREIGN KEY (id) REFERENCES profile(id)
-);
-
 DROP TABLE IF EXISTS profile_links;
 
 CREATE TABLE IF NOT EXISTS profile_links (

migrations/0005_access.sql

@@ -0,0 +1,21 @@
+-- Migration number: 0005 	 2025-01-30T00:58:45.123Z
+
+DROP TABLE IF EXISTS access;
+
+-- Store authentication and authorization data separately from profiles
+CREATE TABLE IF NOT EXISTS access (
+	-- The UUID of the profile this access belongs to
+	id TEXT NOT NULL UNIQUE COLLATE BINARY,
+	-- Schema version to use
+	schemaVersion INTEGER NOT NULL DEFAULT 1,
+	-- The person's access level in the system
+	-- This determines what actions they can perform
+	access_level TEXT NOT NULL CHECK(access_level IN ('admin', 'organizer', 'volunteer')),
+	-- The person's account password
+	password TEXT NOT NULL,
+	-- The person's email address
+	email TEXT NOT NULL UNIQUE,
+
+	PRIMARY KEY (id),
+	FOREIGN KEY (id) REFERENCES profile(id)
+);