[web-32] 인증 API prefix /api/v1/auth 적용 및 Swagger 문서 개선#20
Merged
Conversation
- AuthController: /auth -> /api/v1/auth prefix 변경 - AuthController: @SecurityRequirements 추가 (Swagger 로그인 자물쇠 제거) - AuthController: @ApiErrorExceptions 적용, 기존 verbose @ApiResponses 제거 - SecurityConfig: PUBLIC_URLS /auth/** -> /api/v1/auth/** 변경 - OpenApiConfig: authApi /api/v1/auth/**, adminApi /api/v1/** 경로 통일 - ApiErrorExceptions: ErrorCode 기반 에러 응답 자동 등록 어노테이션 추가 - ApiErrorExceptionCustomizer: OperationCustomizer 구현체 추가
Chunwol
added a commit
that referenced
this pull request
May 24, 2026
[web-32] 인증 API prefix /api/v1/auth 적용 및 Swagger 문서 개선
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
작업 내용p
Auth API의 Swagger 문서를 개선하고 공통 API prefix
/api/v1/를 적용합니다.변경 사항
AuthController요청 경로/auth/**→/api/v1/auth/**변경@SecurityRequirements적용으로 Swagger에서 auth 엔드포인트 자물쇠 제거@ApiResponses제거 →@ApiErrorExceptions커스텀 어노테이션으로 교체SecurityConfigPUBLIC_URLS 및OpenApiConfigpath 패턴/api/v1/auth/**통일OpenApiConfig에NotFound(404)공통 응답 컴포넌트 추가테스트
POST /api/v1/auth/loginSwagger에서 자물쇠 없이 노출 확인POST /api/v1/auth/refresh,POST /api/v1/auth/logout동일 확인