Hi Ben,
Thanks for the changes. I looked over the changes.
Regards,
--Venkat.
On 6/22/05, Ben Alex [EMAIL PROTECTED] wrote:
Venkat Sonnathi wrote:
Hi Ben,
Please find attached the patch for AbstractSecurityInterceptor.java,
Basically, it checks to see if the existing authentication
AbstractSecurityInterceptor.java abstract.patch), so please let me
know if you want me to re-create it in any other specific way.
Thanks,
--Venkat.
On 5/21/05, Ben Alex [EMAIL PROTECTED] wrote:
Venkat Sonnathi wrote:
Would this change be in the next release? I would be glad to help if you
want.
Yes
Hi Ben,
On 5/19/05, Ben Alex [EMAIL PROTECTED] wrote:
Venkat Sonnathi wrote:
I am also a bit puzzled as to why we should reset the flag at the
start of each request? In a typical web app, authentication is done
once per session.
Any pointers to how SecurityContext is propagated for RMI
On 5/18/05, Mansoor, Ghazenfer (EDS) [EMAIL PROTECTED] wrote:
-Original Message-
Mansoor, Ghazenfer (EDS) wrote:
How about adding this check at one central place,
AuthenticationManager?
I am doing this and I do not see any problem. I set the
authenticate to
true after
Hi,
I am exploring AcegiSecurity by following the contacts sample
application. I observed that in
AbstractSecurityInterceptor.beforeInvocation method
authenticationManager.authenticate is being called for every request.
Why is it? Can it be optimized to check if authentication is already
done and
