So you can just built the ui once and always include it in the login page for which ever client as the server should be where you filter/ prevent access to data that's not for the current client.
On Mar 22, 10:41 am, Kyle Baley <kyle.ba...@gmail.com> wrote: > I'm new to GWT and the Java world having been in the .NET space for > about 10 years. Our application will be a multi-tenant one (at least, > to the degree that I understand the definition). We'd like customers > to be able to navigate towww.mysite.com/customerName, then log in > from there. I think I have a handle on how to manage this from the GAE > datastore side but am wondering how to manage this URL mapping in > web.xml for GWT. > > Also, would like to get some opinions on how to manage the > authentication once it's set up. Here's how I see it working: > - User navigates towww.mysite.com/customerName > - System retrieves company data and stores in session and displays > login page > - User logs in. System authenticates user > - For all RPC calls, system verifies user is logged in *and* checks > that the URL matches the company info in the session > > Basically, I want to guard against a user logging into one client > site, then navigating to another. > > Thanks > Kyle -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
