01 / IMPLEMENTATION & CONTRIBUTION
What the work involves
Local variants extend David Andrea/djblackett’s invoice app with bcrypt password checks, signed access tokens, hashed refresh records, rotation/reuse handling, and authentication routes and services.
Technical depth
Prisma-backed refresh records; rotation transactions; HttpOnly cookie transport; GraphQL context/resolver integration; Inversify service boundaries; an alternative repository/token-service design; tests for cookie rotation and preventing refresh tokens in JSON.
The project family
dataannotation/my-projectdataannotation/my-project copydataannotation/invoice-authentication-study/02 / RESULTS
What came out of it
Authentication implementations span browser cookies, GraphQL context, and persistence, with targeted test source for rotation and keeping refresh tokens out of JSON responses.
03 / SUPPORTING EVIDENCE
Follow the source
Implementation notes, project records, and supporting artifacts.
Source context & project scope
Do not present the entire upstream invoice app, its original personal project narrative or CI/CD history as Donald’s work.
Variants differ; do not combine them into a claim that one final implementation contains all safeguards.
Security correctness and concurrency behavior were not independently validated.
Skip timesheets, credentials, personal evaluation metadata and real invoice data.
Production security is not established.
Local credential verification, token issuing and refresh rotation implementation.
SOURCE · 2026-09-17Tests specify HttpOnly rotation and absence of refresh secrets from JSON.
SOURCE · 2026-09-17Alternative repository-based session/auth design; variants grouped.
SOURCE · 2026-09-17