Spring Security 5.5.X only works with spring-security-5.4.xsd schema (XML-based config)

Describe the bug SecurityNamespaceHandler throws BeanDefinitionParsingException when we use version 5.0.X (<= 5.0.18.RELEASE) or 5.1.X (<= 5.1.12.RELEASE) with versioned schema in XML-based configuration. On those branches only spring-security-4.2.xsd can be used (see also 'Workaround').

On branch 5.2 this change skipped directly from 4.2 to 5.2. No updates for 5.0 and 5.1 where provided. So handler is still looking for version 4.2:

private boolean matchesVersionInternal(Element element) {
    String schemaLocation = element.getAttributeNS(
            "http://www.w3.org/2001/XMLSchema-instance", "schemaLocation");
    return schemaLocation.matches("(?m).*spring-security-4\\.2.*.xsd.*")
            || schemaLocation.matches("(?m).*spring-security.xsd.*")
            || !schemaLocation.matches("(?m).*spring-security.*");
}

To Reproduce 1. Use raported version of Spring Security. 2. Use XML-based config. 3. Use (the right) versioned schema (e.g. spring-security-5.0.xsd)

Expected behavior Error free XML parsing, when file is valid against XSD with version compatible with Spring Security version (spring-security-5.0.xsd for 5.0.X and spring-security-5.1.xsd for 5.1.X).

Sample ContextConfig with namespace like below isn't working with 5.0.18.RELEASE (Aug 05, 2020):

<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:security="http://www.springframework.org/schema/security"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="
        http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
        http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-5.0.xsd">
</beans>

Workaround Use unversioned schema.

Comment From: Emkas

I'm very sorry for any mistake in this report (if any). This is the first time I'm reporting something on Github :-)

Comment From: Emkas

Branches 5.0 and 5.1 probably won't be fixed, but it looks like the same is now on 5.5.

Comment From: Emkas

Since originally reported branches (5.0/1) are EOL, I've changed issue title to 5.5 and created a pull request.