Skip to content

Document why CSRF stays disabled in the stateless JWT API [skip deploy] #no-deploy #122

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
SebastianLopezO merged 1 commit into from
Nov 1, 2026
Merged

Document why CSRF stays disabled in the stateless JWT API [skip deploy] #no-deploy #122

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 3 additions & 0 deletions src/main/java/app/smartpot/api/security/config/SecurityConfiguration.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,9 @@ public SecurityFilterChain securityFilterChain(HttpSecurity http, CorsConfig cor
RateLimitingFilter rateLimitingFilter = new RateLimitingFilter(cacheStore, errorWriter, clock, properties);

return http
// Sin CSRF a propósito: la API es sin estado y solo acepta el JWT en la cabecera Authorization; no usa
// cookies de sesión ni CORS con credenciales, así que un sitio ajeno no puede hacer que el navegador
// envíe la credencial por su cuenta. Si algún día la sesión pasa a una cookie, hay que activarlo.
.csrf(AbstractHttpConfigurer::disable)
.cors(cors -> cors.configurationSource(corsConfig))
.httpBasic(AbstractHttpConfigurer::disable)
Expand Down
Loading