Hi All,
Now that we have support for JWT cookie authentication:
How do we protect against CSRF. Normally this is done by the client adding a X-XSRF-TOKEN header to the requests and then Kong can test this value against the csrf value held inside the JWT.
Is this happening, or is there another/better way to protect against CSRF.
Thanks
Stephen