How cortadai/spring-security-poc works
Project type and purpose
• This is a full-stack banking PoC comprising two subprojects:
• bank-app-ui (Angular SPA)
• bank-app-api (Spring Boot REST)
• Purpose: demonstrate secure authentication (JWT + CSRF), session management, token refresh, and basic banking operations (accounts, balances, cards, loans, contacts, notices).
File structure
• Top level:
• bank-app-ui/ → Angular 15+ frontend
• bank-app-api/ → Spring Boot backend
• readme.md → high-level overview
• bank-app-ui:
• src/app/components → feature UIs (login, dashboard, account, balance, etc.)
• src/app/services → HTTP wrappers including auth, login, dashboard, logout
• src/app/interceptors → request interceptor adding JWT & CSRF tokens
• src/app/routeguards → protects routes based on auth state
• bank-app-api:
• src/main/java/com/entelgy/bank/config → Spring Security (filters, providers, TokenProvider, RedisConfig)
• controller, service, repository, model, dto, exception layers → classic layered MVC
• src/main/resources/sql/scripts.sql → DB schema
• RedisConfig & TokenRepository → central token store in Redis
README
• Each subproject’s README details tech stacks and install steps, but overall architecture is not diagrammed; we’ll fill that gap.
Detail
• Don’t lump everything into “backend”—break out the security filters, token provider, controllers, service logic, and data store interactions.
• On the UI, separate route guards, interceptors, and feature modules.