"Craig R. McClanahan" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > On Fri, 31 Jan 2003, Bill Barker wrote: > > > Date: Fri, 31 Jan 2003 22:54:38 -0800 > > From: Bill Barker <[EMAIL PROTECTED]> > > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Re: form-based auth > > > > > > "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote in message > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > > > > > > > On Fri, 31 Jan 2003, Madere, Colin wrote: > > > > > > > Date: Fri, 31 Jan 2003 14:06:27 -0600 > > > > From: "Madere, Colin" <[EMAIL PROTECTED]> > > > > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > > > > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > > > > Subject: form-based auth > > > > > > > > Anyone out there have multiple contexts (or simply multiple webapps) > > > > authenticating with the same form (login form in a single location)? > > > > > > The form login page has to be within the webapp, so this is not possible. > > > > Well, not really true. It's an all-or-nothing thing. If you use > > Single-Sign-On, then your login applies to all webapps once you log on to > > one of them. But, without writing your own custom Valve, you can't pick and > > choose which contexts get to see the login. > > > > It is true that the user's authentication applies to all webapps when you > use SingleSignonValve, but I understood the initial question to be "can I > share a single copy of the form login page across multiple webapps". And > that is something you cannot do -- each app needs their own login page > (since the path for the <form-login-page> element is context-relative, not > server-relative). >
Ok, you've got a point. Still, I routinely get around it (at least on *nix systems), by using sym-links and Entities. > Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
