Closed spring-projects-issues closed 12 years ago
Bruno J. S. Peixoto said:
I replaced the xsd contained in spring-security-config-3.1.0.RC3.jar for correct one and my application worked fine.
Bruno J. S. Peixoto said:
It's not possible declare two authentication-manager bean in security xml!?
Luke Taylor said:
Why are you reporting a critical bug against the GA release of 3.1.0 when you are using version RC3?
Bruno J. S. Peixoto said:
You should thank me for finding bugs to you! It's simple to solve: change the issue priority!
Bruno J. S. Peixoto said:
And change the affect version!
Luke Taylor said:
Sorry, but that doesn't make sense. This feature was introduced in 3.1.0, hence was not available in RC3. So there is no evidence of a bug.
Bruno J. S. Peixoto said:
OK,Luke! I saw the commit October 30 on the issue SEC1847 and made a confusion between the versions. I'll try with 3.1.0.
Greetings.
Bruno J. S. Peixoto (Migrated from SEC-1879) said:
I'm having a problem in configuring differents authentication managers to two http elements. If I try to configure authentication-manager-ref in http element, ocurr the follow exception: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'authentication-manager-ref' is not allowed to appear in element 'security:http'.
In header of my security xml, I'm using http://www.springframework.org/schema/security/spring-security-3.1.xsd. If I put it in browser, the xsd loaded declare the attribute authentication-manager-ref to http element, but the xsd in spring-security-config-3.1.0.RC3.jar doesn't.