Full-Stack
University Course Management System
A university course platform with student/admin roles, secure login and full course management — bcrypt password hashing, JWT sessions and role-based access.
Case study, Full-Stack
A role-based customer access portal: one MySQL database shared by four API-key roles, each with its own row limits, credit allowance and visible fields — enforced on the server.
Context
One customer database, four kinds of callers. Guests should see names only; admins need usage data. AccessDesk puts every permission decision on the server, so the browser never decides what a caller may see.
My role: Full Stack Web Development Assignment 05, Air University Kamra.
Implementation
Every request carries an API key in the x-api-key header; unknown keys get 401 before anything else runs.
One middleware chain enforces action permission, database/table allow-listing and credit balance, each with its own status code.
Row limits and column whitelists are applied per role, and search uses bound parameters — never string-built SQL.
Evidence
The points below summarize the public repository and owner-provided CV where noted. Read the source for implementation details before drawing further conclusions.
Guest, Student, Teacher, Admin — each with row limit and credits.
401 → 403 → 403 → 429 → validated SQL.
Design, API routes, security analysis and verification cases.
Boundaries
Continue exploring