Skip to content

fix: 정상테스트 api를 JwtFilter에서 permit #399

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.

Sign up for GitHub

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

Merged
ParkJiYeoung8297 merged 2 commits into from
Feb 19, 2026
Merged

fix: 정상테스트 api를 JwtFilter에서 permit #399

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bf339bd
fix: 정상테스트 api를 springSecurity에서 permit
ParkJiYeoung8297 Feb 19, 2026
bfb0958
Merge branch 'dev' into fix/spring-security-fix
ParkJiYeoung8297 Feb 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/main/java/com/example/RealMatch/global/config/jwt/JwtAuthenticationFilter.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,8 @@ public class JwtAuthenticationFilter extends OncePerRequestFilter {
"/swagger-ui.html",
"/swagger-resources",
"/actuator",
"/api/v1/auth/refresh"
"/api/v1/auth/refresh",
"/api/test"
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-medium medium

The addition of "/api/test" to EXCLUDED_PATHS combined with the startsWith matching logic in the shouldNotFilter method (line 113) creates a security vulnerability. This causes the JWT authentication filter to be skipped for any request URI starting with "/api/test", inadvertently including the protected /api/test-auth endpoint. Consequently, legitimate authenticated requests to /api/test-auth receive a 401 Unauthorized error, breaking access to protected test endpoints. This also highlights a broader maintainability issue: the EXCLUDED_PATHS list duplicates and is inconsistent with SecurityConfig's PERMIT_ALL_URL_ARRAY. For example, paths like /api/v1/tags/** and /api/v1/auth/signup are permitAll in SecurityConfig but are missing from EXCLUDED_PATHS, potentially leading to incorrect JWT authentication requirements. It is strongly recommended to use a more precise matching mechanism, such as equals() for exact matches or Spring's AntPathMatcher for pattern matching, to ensure only intended paths are excluded. For a more robust solution, consider refactoring to manage all security configurations in a single place, perhaps using WebSecurityCustomizer in SecurityConfig to completely bypass the filter chain for ignored paths, making EXCLUDED_PATHS unnecessary.

);

@Override
Expand Down
Loading