Sidekick

Context

Profiles, gigs, applications, and contracts need to share one authenticated account flow while the client, API, and database run together locally.

What I built

• Implemented ASP.NET Core Identity bearer authentication with an HttpOnly refresh-cookie flow.
• Connected React profile, gig, application, and contract flows to PostgreSQL; Docker Compose starts the client, API, and database with health-aware startup.

Technical approach

• A React client communicates with an ASP.NET Core API using an Entity Framework Core data model backed by PostgreSQL.
• ASP.NET Core Identity supplies bearer authentication and the repository exposes profile, skill, gig, application, and contract entities.
• Docker Compose runs the client, API, and database with a PostgreSQL health check before API startup.
• Kept access credentials in the client flow while storing the refresh credential in an HttpOnly cookie.
• Used the existing Identity endpoint and bearer-token support instead of describing the system as a custom JWT implementation.

Security and verification

• ASP.NET Core Identity handles authentication and security-stamp validation for the refresh flow.
• PostgreSQL persists the marketplace and Identity records.
• The Compose setup includes a health-aware dependency for PostgreSQL and a dedicated API health endpoint.
• The repository includes local setup for the React client, API, PostgreSQL database, and Docker Compose environment.

Current limits

• Bootcamp capstone intended for local demonstration. No public deployment is available.