-
Notifications
You must be signed in to change notification settings - Fork 6k
5.5.X only works with spring-security-5.4.xsd schema (XML-based config) #8974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
in: config
An issue in spring-security-config
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
Milestone
Comments
I'm very sorry for any mistake in this report (if any). This is the first time I'm reporting something on Github :-) |
Branches 5.0 and 5.1 probably won't be fixed, but it looks like the same is now on 5.5. |
Since originally reported branches (5.0/1) are EOL, I've changed issue title to 5.5 and created a pull request. |
Emkas
added a commit
to Emkas/spring-security
that referenced
this issue
Oct 7, 2021
jzheaux
pushed a commit
that referenced
this issue
Oct 13, 2021
jzheaux
added a commit
that referenced
this issue
Oct 13, 2021
jzheaux
added a commit
that referenced
this issue
Oct 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
in: config
An issue in spring-security-config
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
Describe the bug
SecurityNamespaceHandler
throwsBeanDefinitionParsingException
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 onlyspring-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:
To Reproduce
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 andspring-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):Workaround
Use unversioned schema.
The text was updated successfully, but these errors were encountered: