Describe the bug http://www.springframework.org/schema/security/spring-security-oauth2.xsd is gone This breaks startup of all our applications because we rely on getting the XSD files from the spring website, but now the XSD files have been removed.
Could the XSD be fixed urgently in the meantime?
To Reproduce visit http://www.springframework.org/schema/security/spring-security-oauth2.xsd and verify that the XSD is gone
Expected behavior spring-security-oauth2.xsd should be present at http://www.springframework.org/schema/security/spring-security-oauth2.xsd at all time.
References This has happened before in 2020:
- http://www.springframework.org/schema/security/spring-security.xsd is gone!?IN: CONFIG
- Failed to read schema document 'http://www.springframework.org/schema/security/spring-security-oauth2.xsd'STATUS: WAITING-FOR-TRIAGE
- Provide spring-security-5*.xsd for https://www.springframework.org/schema/security/IN: CONFIG
Comment From: lukasondrak96
Check this closed issue: #11357
Comment From: MikeN123
I feel that, given the existing issue with using the XSD from the JAR in the spring-security-oauth project, this is a bit of a weird move. It breaks apps all over the place and there is really no good reason to inflict so much damage...
Comment From: whaan
switching the url from http to https actually fixed the issue for us.
FYI: https://www.springframework.org/schema/security/spring-security-oauth2-2.0.xsd
also returns 404 , page not found, but that is not an issue, because in the spring.schemas file in the META-INF folder, all requests for https\://www.springframework.org/schema/security/spring-security-oauth2.xsd get redirected to org/springframework/security/oauth2/spring-security-oauth2-2.0.xsd
So the XSD doesn't have to looked up from the internet. As long as you use https, it will simply look it up from the classpath
Comment From: jgrandja
@whaan Closing this as a duplicate. Please see comment