CSRF token are by default supported, if you are using standard headers.(for example using spring-security headers)
If the CSRF Token is required, swagger-ui automatically sends the new XSRF-TOKEN during each HTTP REQUEST.
That said - if your XSRF-TOKEN isn't standards-based, you can use a requestInterceptor to manually capture and attach the latest xsrf token to requests programmatically via spring resource transformer:
Also, CSRF is becoming less relevant over time, as browsers add user-agent level support for controls over cross-origin request cookie inclusion.
Starting from release v1.4.4 of springdoc-openapi, a new property is added to enable CSRF support, while using standard header names:
springdoc.swagger-ui.csrf.enabled=true