How cesarandres8911/springboot-user-registration works
Project type and purpose
• This is a backend RESTful microservice built with Spring Boot. Its sole responsibility is user registration, authentication (via JWT), password‐policy configuration, and management of user data. There is no separate frontend; clients interact over HTTP (cURL, Postman, any HTTP-capable UI).
File structure
• Top-level Gradle build files (build.gradle.kts, settings.gradle.kts) and src/main/java/com/example/registration/RegistrationApplication.java bootstrap the Spring Boot app.
• controller/ holds REST endpoints: AuthController, UserController, ConfigurationController.
• service/ contains business logic (UserService, ConfigurationService, PasswordValidationService).
• repository/ defines Spring Data JPA interfaces to persist User, Configuration, ConfigurationType.
• model/ are JPA entities.
• dto/ are request/response payload classes.
• mapper/ are MapStruct interfaces mapping between entities and DTOs.
• security/ includes JWT filter, JWT service, and Spring Security config.
• utils/ are password utilities (regex generator, encoder, validator, configuration type).
• config/ holds OpenAPI and Security configuration classes.
• src/main/resources contains H2 SQL schemas and properties.
• docs/ contains supplemental architecture, database, security, utility documentation.
README for additional insights
• Core flows: register user → validate password → save user → return JWT; login → authenticate → return JWT; configuration endpoints allow runtime password-policy changes.
• Uses H2 in-memory DB, Springdoc OpenAPI for docs, Lombok for boilerplate, SLF4J for logging.