That's the job of the webapp :)
All i see in my point of view is a user / pass checking method to
implement (for information the webapp uses osuser authentification
mecanism. So i have to provide an implementation of
com.opensymphony.user.provider.CredentialsProvider which negociate it
with tomcat
Okay, I see your point.
But, if a user requests a secure page without logging in, how will you
find out? Are you using a Servlet Filter or something?
Poorna
David Delbecq wrote:
Hello Poornachandran,
as i said webapp X manage authentification all by itself (basically
using it's own provide
Hello Poornachandran,
as i said webapp X manage authentification all by itself (basically
using it's own providers, so there is now security constraint and so on
in the web.xml, webapp does not use container managed security, and i
have no control over this, closed source webapp), but it provides
Hi David,
I am just wondering after your app authenticates, are you able to get
not-null from request.getUserPrincipal(). I understand this is how the
container understands that user is logged on or not.
Poorna
David Delbecq wrote:
Hello,
I probably will have the following webapp structur
