Quote Originally Posted by Sture View Post

Are there anyone out there that ran multiple webapps with each their own database but with shared WebAppUser and/or WebAppSession tables?

Are there any foreseeable problems with that?

Would it mean that if a browser hooked up to two different such systems (on the same web-server obviously) could actually share the same session? And thus logging in between webapp switches is unnecessary?

In general, what do you do if a customer has a multitude of webapps but wants one user database?

To sum it up: ????? :-)

Yeah, you can do that. I've running webapps that way at a customer. If you set the cookie to the domain, they can login once and be logged in for both applications. If they do not share the domain you'll need a 'real' SSO thingy, but if you can share the tables and cookies, that should just work.