How gaganvdeveloper/supporting-files works
This repository appears to contain a Spring-based user registration and JWT login service: clients submit credentials, the controller authenticates or saves a user, and successful login returns a signed token. Subsequent requests pass through a JWT filter that validates the token and loads user details. The tree also includes mail and JPA configuration, but no README or mail-sending workflow; the referenced UserRepository implementation is absent, so persistence behavior cannot be traced further.
Main entry points: GlobalController.java User Controller · SecurityConfig.java Security Configuration · JWTAuthFilter.java JWT Filter · CustomUserDetailService.java User Details Service
Components 11
User API
- User Controller
GlobalController.java
JWT Security
- Security Configuration
SecurityConfig.java - JWT Filter
JWTAuthFilter.java - JWT Utilities
JWTUtils.java
User Identity
- User Details Service
CustomUserDetailService.java - User Entity
User.java - User Repository
Integrations
- JPA Configuration
UserConfig.java - SMTP Configuration
MailConfig.java
Other components
- API Client
- SMTP Service
Connections 11
- API Client → User Controller: sends requests
GlobalController.java - User Controller → User Repository: reads and saves
GlobalController.java - User Controller → JWT Utilities: generates token
GlobalController.java - User Controller → Security Configuration: authenticates with
GlobalController.java - Security Configuration → JWT Filter: registers filter
SecurityConfig.java - Security Configuration → User Details Service: configures provider
SecurityConfig.java - JWT Filter → JWT Utilities: validates token
JWTAuthFilter.java - JWT Filter → User Details Service: loads user
JWTAuthFilter.java - User Details Service → User Repository: looks up email
CustomUserDetailService.java - User Repository → User Entity: returns user
- SMTP Configuration → SMTP Service: configures sender
MailConfig.java