wrote:
Hello struts users
I have a really basic security problem and i would like to know what is the
best practice to resolve it.
I have an application with an authentification system and diffrent rights
for diffrent type of user. To add or remove a link/fonctionnality, we simply
declarate the
Hand-rolled security almost always has many holes.
I would suggest using spring security.
Cimballi wrote:
One way to do it it to have a super action with a permission property,
and you set the permission property with a static param in your struts
xml files using the StaticParameters intercepto
> From: cosm...@gmail.com
> Date: Fri, 16 Apr 2010 11:28:05 +0800
> Subject: Re: Basic security problem
> To: user@struts.apache.org; cimba...@cimballi.net
>
> Thank you for answers.
>
> Your method looks good Cimbali. But do you think it would be really better
> th
erceptor interceptor to your stack on
> all protected actions.
>
> Cimballi
>
>
> On Thu, Apr 15, 2010 at 9:39 PM, Kun Niu wrote:
> > You should check the authentication all by yourself in your action.
> >
> > Stephane Cosmeur wrote:
> >>
> >> H
by yourself in your action.
>
> Stephane Cosmeur wrote:
>>
>> Hello struts users
>>
>> I have a really basic security problem and i would like to know what is
>> the
>> best practice to resolve it.
>>
>> I have an application with an authentificatio
You should check the authentication all by yourself in your action.
Stephane Cosmeur wrote:
Hello struts users
I have a really basic security problem and i would like to know what is the
best practice to resolve it.
I have an application with an authentification system and diffrent rights
for
Hello struts users
I have a really basic security problem and i would like to know what is the
best practice to resolve it.
I have an application with an authentification system and diffrent rights
for diffrent type of user. To add or remove a link/fonctionnality, we simply
declarate the element
7 matches
Mail list logo