You know, I think that responsibility may have been moved to the
exceptionTranslationFilter. That's probably not very clear...
Look at what entryPoints you have and look how they're being used.
On Nov 8, 2007 5:42 AM, [EMAIL PROTECTED] wrote:
I looked inside the
I needed to change the authenticationEntryPoint property of the
ExceptionTranslationFilter bean in order to make it work.
Thanks a lot Ray !-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to
I looked inside the acegi-security-sample-contacts-filter.war that came
with acegi 1.0.4
the filter chain in applicationContext-acegi-security.xml is defined as
follows:
bean id=filterChainProxy
class=org.acegisecurity.util.FilterChainProxy
property
Hi acegi users,
maybe someone of you knows the trick
What do I have to change in the contacts sample application in order to
enforce basic authentication only ?
if I remove the authenticationProcessingFilter from the filter chain and
keep basicProcessingFilter only it does not have the
No problem, glad I could help.
That's the trick to remember with Acegi that I think people
misunderstand. The filters that actually handle credentials, like the
BasicProcessingFilter, AuthenticationProcessingFilter,
DigestProcessingFilter only do anything when the credentials are
presented. An
