Hi All- I'm a new user who has been tasked with refactoring a GWT 2.3 application so that it can work behind something like Schibboleth or OpenAM, as well as maintain a it's own authentication page/panel.
Searching the forum, I notice that most people when talking about authentication are suggesting that systems authenticate via some RPC service. This works fine so long as you're not behind a SSO Gateway/ proxy that sticks a user key on as a http header, works fine. Given a requirement that it work in this type of environment, is there a best-practice, GWT-thumbs up way to do this? Are servlet filters still a suggested way to do this? Can I integrate a redirecting servlet filter so that it'll behave with regard to RPC calls(redirecting the whole browser when the RPC call is redirected to the SSO Auth page)? Any suggestions would be approved thanks Mike -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
