Rick,
I recently had a similar problem. Using J2EE security, I was not sure how
to detect a user login. After all, a user can go into ANY protected page,
and I did not want to put the same tag in to EVERY single .JSP page that was
protected.
The solution, at least in my case, came in a form a
Well, let's say for the sake of argument, that it's not
authentication we're talking about. Let's say, instead,
that in order to perform some Action B,
some other Action A must be done first. However, doing A does not
necessarily mean you'll do B next. What's the best way to
remember
This question seems to come up frequently, probably should be in a FAQ.
Using Servlet Filters is one approach. If you are using Struts 1.1 (in
1.0.2 it's slightly different), and want to use a Struts approach, try
the following.
I have an application that requires everyone to log in and
Why not use J2EE/WEB standard container authentication? It will do what you
want. In fact, it was designed to do what you want, which is called Lazy,
or just in time, authentication. The user can surf your page, however, when
he links to a protected item, a login page (of your choosing) will
4 matches
Mail list logo
