You'll want to create a session that hangs onto some sort of login information,
either a boolean that states whether the user is logged in, or a bean defined login
object. Next step is to write a small jsp that will be used as a header for all of
your other jsp files. This header will check to make sure the user is logged in,
that they haven't exceed their max idle time etc, otherwise it will return them
back to the login page. Its not the most elegant solution but I've used it before
and it works.
Regards,
Fz
"Thomas, Ian" wrote:
> Greetings illustrious list members,
>
> I hope you guys don't mind a rookie type question, as I'm about to ask one.
>
> I am new to JSP, and thought I would learn by converting an existing
> application using ASP to use JSP. As I suspected would happen, I've run
> into trouble almost immediately.
>
> The effect I'm looking for is this: there is one login page, and then the
> rest of the site. If you go to any page in the rest of the site without
> first having logged in at the login page, you get redirected to an error
> page. I can't figure out how to do this with JSP. I know I could do it
> using a bean or two, but I'm trying to avoid that, as a) I want to duplicate
> as much as possible the functionality of the ASP, meaning no beans, and b)
> I'm pretty new to beans as well, and don't wanna mess with it *grin*.
>
> I tried using pageContext to set a session-scope parameter, but that didn't
> seem to work. I tried using jsp:forward with a jsp:param, then using
> request.getParameter in the protected page, but that REALLY didn't work.
>
> So... what is the best strategy to accomplish this?
>
> -Ian Thomas
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
