How praveen-kumar-karthikeyan/healthy.option.api.user-service works
This is a small Spring Boot user-service exposing /hello and /home. The application entry point starts Spring; Spring maps requests to the controller and applies the configured security chain. Despite the /hello method’s publicApi name, the security configuration requires authentication for every path. Credentials are held in memory. The excerpts show the application, routes, and security setup; framework dispatch details are inferred from Spring annotations and configuration.
Main entry points: SecurityConfig.java Security policy · UserController.java User routes · UserServiceAPI.java Application entry
Components 6
Web service
- Application entry
api.user-service/src/main/java/com/healthy/option/api/user_service/UserServiceAPI.java - User routes
api.user-service/src/main/java/com/healthy/option/api/user_service/controller/UserController.java
Authentication
- Security policy
api.user-service/src/main/java/com/healthy/option/api/user_service/config/SecurityConfig.java - In-memory users
api.user-service/src/main/java/com/healthy/option/api/user_service/config/SecurityConfig.java
Other components
- HTTP client
- Spring runtime
Connections 6
- Application entry → Spring runtime: starts
api.user-service/src/main/java/com/healthy/option/api/user_service/UserServiceAPI.java - HTTP client → Spring runtime: sends requests
- Spring runtime → User routes: dispatches routes
- Spring runtime → Security policy: loads configuration
- Security policy → In-memory users: provides users
api.user-service/src/main/java/com/healthy/option/api/user_service/config/SecurityConfig.java - Security policy → User routes: requires authentication