I am reading the (2.3) spec and am realizing that I am not able to
share a login page with multiple contexts.
In our (embedded) use of Tomcat, we have different contexts, but
we use a single login form/screen.
When configuring the web.xml for those contexts, I realize that there is
no way to have a successful form-login-page without it belonging to the
same context.
In our case, the login form is actually a servlet that belongs to the
default context.
I was hoping to be able to point at that (default context /login)
servlet from the other contexts.
One of the solutions could be to define a /login (the same) servlet
on all the various contexts.
(I will mention that I am defining my contexts as 'trusted').
(Another note: I am using 3.2)
If I do what mention in the last paragraph, I will end up with having
three different instances of the login servlet, right ?
------
An alternate approach could be to define 'login.html' files in those
contexts, and to have that file perform a Location redirect to the
default-context /login servlet.
------
I am wondering about the reasons that may have forced the definition
of a context-relative login-form as opposed to allowing a URL to be
specified.
Arieh
--
Arieh Markel Sun Microsystems Inc.
Network Storage 500 Eldorado Blvd. MS UBRM11-194
e-mail: [EMAIL PROTECTED] Broomfield, CO 80021
Let's go Panthers !!!! Phone: (303) 272-8547 x78547
(e-mail me with subject SEND PUBLIC KEY to get public key)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
