Revert "[Player] Player 레이어드 구조 리펙토링 (#163)" (#172)

[Jeong-Rae]

This reverts commit 28ed87d.

[chatgpt-codex-connector]

💡 Codex Review

MasterServer/src/main/java/org/codequistify/master/domain/player/service/PlayerDetailsService.java

Lines 37 to 41 in 69a9f49

	@Transactional
	@LogExecutionTime
	public UserDetails loadUserByUsername(String username) throws UsernameNotFoundException {
	LOGGER.info("[loadUserByUsername] loadUserByUsername: {}", username);
	return playerRepository.getPlayerByUid(username);

Handle missing user in loadUserByUsername

When the JWT audience contains a UID that does not exist (e.g., a forged or stale token), playerRepository.getPlayerByUid returns null, but loadUserByUsername just forwards that value. AuthenticationTokenFilter then builds a UsernamePasswordAuthenticationToken with the returned user and immediately dereferences userDetails.getAuthorities() (AuthenticationTokenFilter.java lines 67-69), which will throw a NullPointerException and return a 500 instead of a 401. This regression came from the revert; the previous UserDetailsService threw on missing users. The method should raise an authentication error when no player is found instead of returning null.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".