With Acegi, are you using an interceptor or is there a different way to
enforce security?  I wouldn't mind seeing an example of this if there's one
that you can point to.  IMO, this would fit into Struts 2 authentication
best practices and a little page describing the general setup wouldn't be a
bad idea.
Thanks,
Tom


Gary Affonso wrote:
> 
> Dave Newton wrote:
>> Interceptor or Acegi.
> 
> +1 on Acegi.
> 
> We've been doing auth "by hand" for years, I think we've used just about 
> every technique over time (writing servlet filters, writing WebWork 
> interceptors, doing checks in the Action's exec method, using 
> container-security, etc).
> 
> But having just climbed the Acegi learning curve (it wasn't as bad as I 
> feared, particularly if you already know Spring) I can say that, for us, 
> it's absolutely the best thing we could be doing.  Should have done it 
> years ago.
> 
> - Gary
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Login-checking-before-processing-any-action-class-tf4754010.html#a13596932
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to