fix: /reissue api에서 발생한 SecurityCustomException을 처리해줄 수 있도록 한다. (#348)

api/src/main/java/com/sponus/sponusbe/global/exception/GlobalExceptionHandler.java

@@ -14,6 +14,7 @@
 import com.sponus.coredomain.domain.common.ApiResponse;
 import com.sponus.coredomain.domain.common.BaseErrorCode;
 import com.sponus.coredomain.domain.common.GlobalErrorCode;
+import com.sponus.coreinfrasecurity.jwt.exception.SecurityCustomException;
 import com.sponus.sponusbe.domain.organization.exception.OrganizationErrorCode;
 
 import lombok.extern.slf4j.Slf4j;
@@ -34,6 +35,17 @@ public ResponseEntity<ApiResponse<String>> handleAllException(Exception e) {
 		return ResponseEntity.internalServerError().body(errorResponse);
 	}
 
+	@ExceptionHandler({SecurityCustomException.class})
+	public ApiResponse<Object> handleSecurityCustomException(SecurityCustomException e) {
+		log.warn(">>>>> SecurityCustomException occurred in servlet: {}", e.getErrorCode());
+		BaseErrorCode errorCode = e.getErrorCode();
+		return ApiResponse.onFailure(
+			errorCode.getCode(),
+			errorCode.getMessage(),
+			e.getMessage()
+		);
+	}
+
 	@ExceptionHandler({CustomException.class})
 	public ResponseEntity<ApiResponse<Void>> handleCustomException(CustomException e) {
 		BaseErrorCode errorCode = e.getErrorCode();