How bevia/authmicroservice works
Project Type and Purpose
• Type: A standalone Spring Boot microservice whose sole responsibility is authentication and authorization via JWTs.
• Purpose:
– Expose REST endpoints for user signup/login
– Issue signed JWTs (via JJWT)
– Serve user/role data to downstream services
– Allow stateless validation of tokens by other microservices
File Structure
Top-level:
• pom.xml, mvnw/* – Maven build & wrapper
• src/main/java/org/example/authmicroservice
– AuthMicroservice.java (entry point)
– controller/AuthController.java (REST API)
– jwt/JwtUtils.java (token generation/validation)
– security/WebSecurityConfig.java (Spring Security setup)
– service/UserDetailsServiceImpl.java, UserDetailsImpl.java (user lookup & principal)
– model/{User,Role,ERole} (JPA entities & enums)
– repository/{UserRepository, RoleRepository}
– payload/request + payload/response DTOs
• src/main/resources/application.properties (DB & JWT secret)
• src/test/... – unit tests
README Insights
• Core responsibilities: user management, credential verification, JWT issuance.
• Key tech: Spring Security, Spring Web, Spring Data JPA, JJWT, BCrypt, in-memory H2 (dev).
• JWT is stateless; optionally an introspection endpoint can be added.
• Downstream services (Order, Payment) validate tokens using shared secret & custom filter.
A. System Context (Highest Level)
– Actors:
• Client (e.g. Web/Mobile UI or API Gateway)
• Downstream Microservices (Order Service, Payment Service, etc.)
– System: Authentication Microservice
– External Dependencies:
• Relational Database (H2/MySQL/PostgreSQL)
• (Optional) API Gateway or Service Registry
1. REST API Layer
• AuthController
2. Security Layer
• WebSecurityConfig (filter chain config)
• JwtAuthenticationFilter (custom OncePerRequestFilter)
3. Service Layer
• UserDetailsServiceImpl / UserDetailsImpl
• JwtUtils
4. Persistence Layer
• Spring Data JPA Repositories (UserRepository, RoleRepository)
• JPA Entities (User, Role, ERole)
5. Data Store
• Relational DB
Client → AuthController → Security Filter → Service → Repository → DB
Service → JwtUtils → (signs token) → AuthController → Client
If desired, break out components such as:
• JwtUtils: methods generateToken(), validateToken(), parseClaims()
• WebSecurityConfig: chain of filters, password encoder bean
• AuthController: endpoints /api/auth/signup, /api/auth/signin
• DTO layer: request/response payloads
Relationships & Interactions
• Client calls /signup or /signin.
• AuthController delegates to AuthenticationManager (Spring Security) & UserDetailsServiceImpl.
• On success, JwtUtils builds a JWT, returned in JwtResponse.
• Client stores JWT and uses it for subsequent requests to other services.
• Downstream services independently validate JWT via their own filter using shared secret.
• (Optional) Downstream calls GET /users/{id} on Auth Service for enriched user data.
Architectural Patterns & Design Principles
• Layered Architecture (Controller → Service → Repository)
• Microservice (single‐responsibility, stateless)
• JWT as stateless token format
• Dependency Injection (Spring)
• Externalized configuration (application.properties)
• Secure password hashing (BCrypt)
• Use of interfaces for extensibility (UserDetailsService)