-
Notifications
You must be signed in to change notification settings - Fork 1
feat: replace CustomRuntimeException with SecurityException for exist… #340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ing Mosu users in OAuthUserService
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @jbh010204, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request refactors the exception handling within the OAuthUserService. The primary change involves replacing a custom runtime exception with a standard Java security exception when an existing Mosu user attempts to log in via OAuth. This aims to standardize the exception type for this specific scenario, improving consistency with Java's built-in exception hierarchy.
Highlights
- Exception Type Refactoring: The CustomRuntimeException, previously used for signaling an existing Mosu user during OAuth login, has been replaced with the standard Java SecurityException.
- Code Clean-up: The imports for CustomRuntimeException and ErrorCode were removed from OAuthUserService.java as they are no longer utilized after the exception type change.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
안녕하세요. CustomRuntimeException을 SecurityException으로 변경하여 기존 모수 회원의 OAuth 로그인 시도를 처리하는 변경 사항을 확인했습니다. 이 변경으로 기존의 사용자 정의 예외 처리 방식에서 스프링 시큐리티의 인증 실패 처리 흐름을 따르도록 의도하신 것으로 보입니다. 좋은 방향의 변경이라고 생각합니다. 다만, SecurityException은 다소 일반적인 예외이므로, 스프링 시큐리티에서 제공하는 더 명확한 의미의 예외를 사용하는 것을 제안합니다. 자세한 내용은 코드 리뷰 댓글을 참고해주세요.
| if (oAuthUser.isMosuUser()) { | ||
| log.info("모수 회원으로 가입된 사용자입니다: {}", oAuthUser.getLoginId()); | ||
| throw new CustomRuntimeException(ErrorCode.ALREADY_MOSU_USER); | ||
| throw new SecurityException(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
현재 SecurityException을 사용하고 계신데, 이 예외는 자바 보안 모델과 관련이 깊어 현재 컨텍스트에는 의미가 명확하게 와닿지 않을 수 있습니다.
스프링 시큐리티의 예외 계층 구조를 활용하여 더 의미가 명확한 예외를 사용하는 것을 추천합니다. 예를 들어, AuthenticationServiceException은 인증 처리 중 발생하는 서비스 레벨의 문제를 나타내는 데 사용됩니다. "이미 가입된 사용자가 소셜 로그인을 시도하는 경우"를 서비스 로직 상의 인증 실패 케이스로 보고 이 예외를 사용하면 코드의 의도를 더 잘 드러낼 수 있습니다.
이렇게 변경하면 스프링 시큐리티의 표준 인증 실패 처리 흐름을 따르면서도, 나중에 코드를 유지보수할 때 예외의 원인을 파악하기 용이해집니다.
다음과 같이 변경하는 것을 제안합니다. (이 경우 org.springframework.security.authentication.AuthenticationServiceException 임포트가 필요합니다.)
| throw new SecurityException(); | |
| throw new AuthenticationServiceException("모수 회원으로 가입된 사용자입니다. 일반 로그인을 이용해주세요."); |
…ing Mosu users in OAuthUserService
✨ 구현한 기능
📢 논의하고 싶은 내용
🎸 기타