Saturday, July 9, 2011

Re: Spring Security with GWT

This is because GWT uses an IFRAME to submit by default. There's no
reason it has to be a form to submit to your logout URL, so I'd just
do an anchor link as kellizer suggests or just do a
Window.Location.replace("/j_spring_security_logout") when your button
is pressed. That will redirect the whole application to your logout
URL.

On Jul 8, 4:27 pm, Sven <sven.reinhard...@googlemail.com> wrote:
> Hi people,
>
> I am using GWT 2.3 and Spring Security 3. To explain my application
> structure a little bit. My WebContent folder contains:
>
> WebContent/
> ---------WEB-INF/
> ---------login.html
> ---------logout.html
> ---------secure/
> -------------------index.html
>
> Starting my application and trying to accesshttp://127.0.0.1.:8888/secure/index.html
> redirects me tohttp://127.0.0.1.:8888/login.html... That's the way it
> should be. After entering my credentials I get taken to my secured
> index.html. There I have a navigation bar containing a FormPanel which
> fires a POST j_spring_security_logout.
>
> My configuration says that in this case I should get taken tohttp://127.0.0.1.:8888/logout.html.
> The security log shows that the security chain is processing a
> redirect to this page. But the strange behaviour I stay on the secured
> index page in FF or IE.
>
> Obviously something blocks the redirect or do I have a general
> missunderstanding?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate