It's not immediately apparent how to get RestGWT's FilterAwareDispatcher working seamlessly with Spring Security's CsrfFilter. On form submit, the response is always a 403. This is b/c the token is not initially set (either via meta tag or a hidden form field). How to bootstrap the token value (client-side) is what's presently mysterious.
It's not immediately apparent how to get RestGWT's FilterAwareDispatcher working seamlessly with Spring Security's CsrfFilter. On form submit, the response is always a 403. This is b/c the token is not initially set (either via meta tag or a hidden form field). How to bootstrap the token value (client-side) is what's presently mysterious.
Reading: