SEC-1847: Allow use of custom AuthenticationManager in <http> and <global-method-security> #2084

Closed
spring-issuemaster opened this Issue Oct 30, 2011 · 2 comments

1 participant

@spring-issuemaster

Luke Taylor (Migrated from SEC-1847) said:

Since it is now possible to have mutiple filter chains in the namespace, may be more convenient to use different AuthenticationManager configurations for each filter chain, or even to implement the AuthenticationManager interface and not have to deal with AuthentiationProvider implementations. It would make sense to provide a hook in the namespace elements to facilitate this.

@spring-issuemaster

Agustin Lopez said:

Hi Luke,

I saw that you fixed this recently. I downloaded and compiled the latest snapshot of Spring Security in order to use a different Authentication Manager for each http tag but as this is not documented I am not sure how should I handle this.

Could you please explain a little about it?

I currently have this:










with a single:





How can I create a new one and assign each of them to each http tag?

Thank you very much in advance,
Agustin

@spring-issuemaster

Bruno J. S. Peixoto said:

Hi All,

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.

@spring-issuemaster spring-issuemaster added this to the 3.1.0 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment