Hello, JSP-ers!
I'm interested in how people have worked around the broken "forward"
directive in Sun's JaWS-based JSP (JSP1.0 beta in the JaWS 2.0 beta, as I
remember) ...specifically in handling "logging in".
I'd like to have my JSP pages include a "standard" 1-2-or-3-liner near the
top that calls something (on the order of "sessionBean.verify(request)) to
ensure that the user gets sent to a login page if they haven't yet got a
"user" bean instantiated in their session.
I'd also like the user to be able to bookmark any page, and then return
there days later; returning would involve getting detoured through the
login page first, and then returned to the original (bookmarked) URL after
entering a user-id and password. That same "sessionBean.verify(request)"
call would realize that it should use the username and password from the
request to try to get a userBean [via some back-end prepared to
authenticate users]
All in all, this seems like it'd be a simple yet sufficient login approach,
if forward worked. Is anyone willing to share the general approach,
infrastructure, or even the code you've used to handle user authentication?
I don't need, or want to know, the low-level "password matching" part, only
the organization of the clients of that authentication part.
Regards, and thanks in advance!
-Paul
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
