Dear all,
we have some very odd behaviour here.
First the basic:
- Tomcat 5.5.17
- Debian Sarge
- Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
We do have several Sevlets which require and use FormBased Login using
Tomcat's internal FormAuthenticator.
Now we've
The servlet is mapped to /
The security constraint is mapped to /*
That's your problem. Map your security constraint to * instead
Gregor Schneider a écrit :
Dear all,
we have some very odd behaviour here.
First the basic:
- Tomcat 5.5.17
- Debian Sarge
- Java(TM) 2 Runtime Environment,
Hi Joshua,
1st, thanks a lot for your quick answer, we really do appreciate it.
However, this does not seem to be the cause of our problem.
We changed the mapping in our web.xml both (security constraint AND
servletmapping) to /* - same result, no login-screen. Then we
changed it to / (both
Hi David,
unfortunately your suggestion did not solve the problem, any other
suggestions are appreciated
merci !
Greetings
Yassine
On 9/13/06, David Delbecq [EMAIL PROTECTED] wrote:
The servlet is mapped to /
The security constraint is mapped to /*
That's your problem. Map your security
Argl... mixed up Joshua from Apache and David from Tomcat - sorry 4
that, both are legends anyways...
Cheers!
Greg
--
what's puzzlin' you, is the nature of my game
-
To start a new topic, e-mail: users@tomcat.apache.org
To
Hi,
we got Authentication working now, however, there's a caveeat:
We just removed the context-file in
$catalina_home/conf/Catalina/localhost/SingleSignon.xml, and now it
starts.
What we do not understand is:
Why does an existing context-definition enable a servlet to bypass
FormBased
Dear all,
no, this is not a one2one-conversation, we succeeded, however, there
appears to be a bug in Tomcat. Before we're submitting this one, I'd
like to have your oppinions - maybe we're missing something here.
As you may have read, the basics:
- Tomcat 5.5.17
- Debian Sarge
- Java(TM) 2
