> I'm using JSecurity and the Grails plugin for the first time on a new > project and I'm running into an issue where my user is filling out a long > form and is timing out. When they hit the submit button, they get > redirected to the login page, but once they log back in they have lost > everything they did. Is there a way to configure JSecurity so that it is > able to save this request and then complete it once they log back in? I > have used Acegi in the past and it does this, so I was expecting it to "just > work." > Any help would be greatly appreciated!
Ah yes, that old chestnut. I believe there is an outstanding issue for this. It's a non-trivial problem, and I'd be interested to know how Spring Security does it. One approach is to return an HTML page containing the POST data in a form with a little bit of javascript to auto-submit that form. Another approach would be to invoke the corresponding action directly, but I'm not sure there is a clean way to do this. It may be easy to do now with the new "forward()" method that has been added to Grails 1.1, but I haven't looked into it. JSecurity itself may have a solution, in which case you could use the native interceptors rather than the plugin's filter-based system. Cheers, Peter
