Shekher wrote:
>
> I am planing to use interceptor for this but not sure how to plan this
>
> as using interceptor can not gurantee a robust authenticate mechanism
> what i planned is as below
>
> if user provide the valid information store the user object in the session
> scoped map and for a
I agree with Andy Law, Interceptors is much better, and you can
implement your security as you want. To my applications I use an
object in a Session Scope and check if it still exists... if not...
redirect to login action.. simple and easy.
On Mon, Dec 15, 2008 at 10:35 AM, shekher awasthi
wrote:
I am planing to use interceptor for this but not sure how to plan this
as using interceptor can not gurantee a robust authenticate mechanism
what i planned is as below
if user provide the valid information store the user object in the session
scoped map and for all incoming request to secure regi
Shekher wrote:
>
> Hi All,
>
> We are developing an application based on Struts2 framework. We are on way
> to develop application based security so that the unauthorized user can
> not
> access the secure area,it needs the request to be from the authorized
> person.We can have the Below mentio
Thanks for the detailed reply, i fear we don't know much about Spring frame
work but can use the approach for our application
other suggestions are also most welcomed
On Mon, Dec 15, 2008 at 5:26 PM, Fogleson, Allen <
allen.fogle...@daugherty.com> wrote:
> We have a similar system of application
We have a similar system of application security. What we do is create session
scoped user object in our spring application.xml, then use a servlet filter to
see if the user is there. The servlet filter redirects to login.action if the
user is attempting to access a protected resource. Here are
6 matches
Mail list logo
