To implement the logging functionality as requested, we'll need to create a new service for handling the logs and modify the existing code to use this service. We'll use a combination of a new Java file for the logging service and quick edits to existing files.

Let's start by creating a new LoggingService:

These changes will create a new log file in the src/main/resources/static directory named user_activity.log. This file will contain JSON-formatted log entries for user logins and subsequent API calls using the generated token.

The log entries will include:

1. Timestamp
2. User ID
3. Username
4. Request details
5. Response details (for login) or "API Call" (for subsequent requests)

Make sure to update any dependency injection configurations if necessary to accommodate the new LoggingService.

Based on the changes we've made to implement the logging functionality, most of the other classes can remain the same. However, we need to make a few minor adjustments to ensure everything works correctly with the new LoggingService. Let's go through the necessary changes:

1. Update the AuthController to inject the LoggingService:

These changes ensure that the LoggingService is properly injected and used in the necessary components. The rest of the classes, including UserRepository, LoginDataDto, LoginRequestDto, LoginResponseDto, and RoleDto, can remain unchanged as they don't directly interact with the logging functionality.

Remember to update your main application class to enable component scanning for the new LoggingService if it's in a different package:

With these changes, your application should now log user activities, including logins and subsequent API calls, to the specified log file while maintaining the existing functionality.