Ben Wrote : If you have \A/secure/.*\Z=ROLE_SUPERVISOR,ROLE_TELLER in filterInvocationInterceptor, it is entirely correct that a user only holding ROLE_ABC should receive a 404 error. Add a comma and the ROLE_ABC if you want to allow users holding ROLE_ABC to access the /secure URIs. If that doesn't work, I'd suggest turning on debugging to see what ContextHolder.getContext().getAuthentication().getAuthorities() actually contains. ------- I want to get rid of this line in filterInvocationInterceptor. If ROLE_ABC is included in this line, then things work out smoothly, but then it means that in future If I will be adding a new role in descriptor I have to restart my context ( tomcat ) , is there any way through which role can be added in secureContext without restarting the server.
Regards, Sami Ather -------------------------------------------------- System Developer Product Development & Engineering AUSTAR Communications Pty Ltd Ph : 02 9394 9511 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ********************************************************************** ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Acegisecurity-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
