Hi Mark,
i don't know the details, but in general when You was redirecting to
L1 or Ln You had the knowlegde about requested page P, so just
redirect to this centralized solution but store two things, what was
requested (page P and maybe also parameters) and some identificator of
a user (session
- L1 --- forward -- C --- forward -- P
From: Paweł Wielgus poulw...@gmail.com
Reply-To: Struts Users Mailing List user@struts.apache.org
Date: Thu, 29 Apr 2010 08:44:29 -0500
To: Struts Users Mailing List user@struts.apache.org
Subject: Re: Login redirection
Hi Mark
2010 08:44:29 -0500
To: Struts Users Mailing List user@struts.apache.org
Subject: Re: Login redirection
Hi Mark,
i don't know the details, but in general when You was redirecting to
L1 or Ln You had the knowlegde about requested page P, so just
redirect to this centralized solution but store two
I am working on a Struts 1.x application that has a number of login pages L1,
L2, L3, ... If a non-authenticated user requests a page - P - that requires
authentication, the user will be redirected to one of these login pages L1, L2,
L3, ... - depending on the context. Once authenticated, he
Hi Mark,
To implement security across multiples applications (Struts or non
Struts), you will have to rely on the container. The container is really
the best way to go if you want to implement a cross applications sign-on.
Now, about your specific question, I guess we are missing some
5 matches
Mail list logo
