Permissions by role
JWT and role-based authorization define permitted operations. Public registration supports buyers and sellers; administrators are provisioned separately.
CASE STUDYFULL-STACK
KeysHaven
From catalog to digital key.
Project · Collaborative · simulated payments
JavaSpring BootSQLMySQLReactJavaScriptViteRedux ToolkitTesting
Overview
A digital-key marketplace connecting catalog, inventory and orders.
Collaborative e-commerce with cart, accounts and seller/admin panels. The purchase experience uses a simulated payment workflow.
Problem
Connect catalog, roles and key inventory with a consistent order workflow.
My role
I contributed to the team project, working on backend authorization, business consistency, and security and order tests.
Architecture
React/Vite SPA with Redux Toolkit → Java/Spring Boot REST API → services and JPA/Hibernate → MySQL. The API assigns inventory keys to order items.
Technical decisions
A cart tied to the user
The cart belongs to the account and is restored with the session. The backend assigns inventory keys to order items; payment remains simulated.
Challenges and solutions
Restrict order and discount operations by user and role, and preserve consistency between inventory and business rules. The backend includes authorization regression tests.
Outcomes
Client-server solution connecting catalog, cart, keys and orders. Contributions include authorization controls and regression tests. The purchase flow is a demonstration, with no real sales or customers.