Re:Stop using JWT for sessions
by factcheckers on Wednesday October 11, 2017 @06:41PM
(#15454188)
This line is just incorrect:
> The only correct CSRF mitigation is a CSRF token
Custom headers are better, imho, if you have an ajax-driven app. There is 0 chance of csrf ever happening if you require the session token be passed in a custom header and hold the session value in localstorage.
> The only correct CSRF mitigation is a CSRF token
Custom headers are better, imho, if you have an ajax-driven app. There is 0 chance of csrf ever happening if you require the session token be passed in a custom header and hold the session value in localstorage.
Source: I am an infosec professional.