+1  A: 

If you are getting a 403 code, means that the user does not have the required roles. So, athentication is not the problem, is authorization.
The only way to know what is going on is to put logging level to debug, there should be more info. Post it here.
Does your roles has de ROLE_ prefix?

rodrigoap
Good points, sorry about the bonehead post, been too tired and distracted to think straight :-(
vector
A: 

... figured it out. Despite having ROLE_TEST specified in the config file and the same in the 'authority' column of the db, Spring-Sec was expecting ROLE_SUPERVISOR:

[DEBUG,AbstractSecurityInterceptor,http-8084-7] Secure object: FilterInvocation: URL: /admin/test.jsp; ConfigAttributes: [ROLE_TEST]
[DEBUG,AbstractSecurityInterceptor,http-8084-7] Previously Authenticated: org.springframework.security.providers.UsernamePasswordAuthenticationToken@af840ed7: Principal: org.springframework.security.userdetails.User@3ec100: Username: testUser; Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: ROLE_SUPERVISOR; Password: [PROTECTED]; Authenticated: true; Details: org.springframework.security.ui.WebAuthenticationDetails@1c07a: RemoteIpAddress: 127.0.0.1; SessionId: 350B260FAFDDBF04D5CB4AAAB7B8A441; Granted Authorities: ROLE_SUPERVISOR
[DEBUG,ExceptionTranslationFilter,http-8084-7] Access is denied (user is not anonymous); delegating to AccessDeniedHandler
org.springframework.security.AccessDeniedException: Access is denied
        at org.springframework.security.vote.AffirmativeBased.decide(AffirmativeBased.java:68)

... now I'm curious, how come? So after changing ROLE_TEST to ROLE_SUPERVISOR in the config file all worked as expected.

vector
.... I realized today that all this time I was looking at the wrong db, 'nough said.Thaks a bunch though, it did help!
vector

related questions