What about just storing usernames internally as [email protected] and [email protected]? When the user is authenticating, simply append the domain name they are authenticating within to their username. This might be restricting usernames to not include the @ symbol.
On Tue, Sep 6, 2011 at 10:32 AM, wmjasonward <[email protected]> wrote: > I'm creating a webapp that will be white-labeled and I need to allow > different domains to have overlapping usernames. For example, www.a.comand > www.b.com could both have users named 'jason' even though both domains are > being serviced by the same underlying webapp (using Tomcat). The user > 'jason' on domain www.b.com is a different person than the user 'jason' on > www.a.com. > > Also, I'll be using a database to store user information. I prefer to work > with the Stable Shiro 1.1 but will consider moving up to Shiro 1.2 if it > makes this task easier and the functions I need are stable. > > I'm just getting started with Shiro and am of course on a compressed > timeline so I'd appreciate any help getting me pointed in the right > direction on how to do this (wrap the filter, override the realm, etc.). > > Thanks! > Jason > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Include-domain-in-user-authentication-tp6764853p6764853.html > Sent from the Shiro User mailing list archive at Nabble.com. >
