How pereiraadiel/challenge-based-auth works
This is a web application for authentication using user-selected word, image, or number sets. Users register and receive a secret set, request a challenge, select groups containing their secret elements, and authenticate; authenticated users can view or change their set. The graph preserves the sampled client/server calls and domain stages. The README is empty, and unsampled routes and module bindings are represented only where the source index supports them; uncertain wiring is omitted.
Main entry points: app Next.js pages · authenticateUser.service.ts Sign-in challenge · users.service.ts User lifecycle · redis.provider.ts Redis provider
Components 22
Web client
- Next.js pages
client/src/app - UI components
client/src/app/components - Local session
client/src/hooks/useLocalStorage.ts - HTTP API client
client/src/utils/api.util.ts - User contracts
client/src/app/contracts/user.contract.ts
API and domain
- Auth controller
server/src/infra/controllers/auth.controller.ts - Users controller
server/src/infra/controllers/users.controller.ts - Sign-in challenge
server/src/domain/services/authenticateUser.service.ts - User lifecycle
server/src/domain/services/users.service.ts - Set generation
server/src/domain/utils/set.util.ts - User mapping
server/src/domain/mappers/users.mapper.ts - User entity
server/src/domain/entities/user.entity.ts - Repository contracts
server/src/domain/contracts/repositories - Auth guard
server/src/infra/guards/auth.guard.ts - Auth interceptor
server/src/infra/interceptors/auth.interceptor.ts - App module
server/src/infra/modules/app.module.ts
Redis storage
- Auth cache
server/src/infra/repositories/auth.cache.repository.ts - Token cache
server/src/infra/repositories/token.cache.repository.ts - User cache
server/src/infra/repositories/users.cache.repository.ts - Redis provider
server/src/infra/providers/redis.provider.ts
Other components
- Visitor
- Redis
Connections 22
- Visitor → Next.js pages: uses
client/src/app/page.tsx - Next.js pages → UI components: renders
client/src/app/page.tsx - Next.js pages → Local session: stores session
client/src/app/page.tsx - Next.js pages → HTTP API client: requests
client/src/app/page.tsx - HTTP API client → Auth controller: calls auth
- HTTP API client → Users controller: calls users
- Auth controller → Sign-in challenge: delegates
server/src/infra/controllers/auth.controller.ts - Users controller → User lifecycle: delegates
server/src/infra/controllers/users.controller.ts - Sign-in challenge → Repository contracts: uses repositories
server/src/domain/services/authenticateUser.service.ts - User lifecycle → Repository contracts: uses repositories
server/src/domain/services/users.service.ts - Sign-in challenge → Set generation: builds challenge
server/src/domain/services/authenticateUser.service.ts - Sign-in challenge → User mapping: maps secret set
server/src/domain/services/authenticateUser.service.ts - User lifecycle → Set generation: generates user set
server/src/domain/services/users.service.ts - User lifecycle → User mapping: maps responses
server/src/domain/services/users.service.ts - User mapping → User entity: maps entity
server/src/domain/mappers/users.mapper.ts - Auth cache → Redis provider: reads and writes
server/src/infra/repositories/auth.cache.repository.ts - Token cache → Redis provider: reads and writes
server/src/infra/repositories/token.cache.repository.ts - User cache → Redis provider: reads and writes
server/src/infra/repositories/users.cache.repository.ts - Redis provider → Redis: stores data
server/src/infra/providers/redis.provider.ts - App module → Auth guard: registers guard
server/src/infra/modules/app.module.ts - Users controller → Auth interceptor: uses interceptor
server/src/infra/controllers/users.controller.ts - App module → Auth interceptor: imports
server/src/infra/modules/app.module.ts