You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
11:27:28.510 [localhost-startStop-1] WARN o.s.b.f.xml.XmlBeanDefinitionReader - Ignored XML validation warning
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://www.springframework.org/schema/security/spring-security.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[…]
11:27:28.614 [localhost-startStop-1] ERROR o.s.web.context.ContextLoader - Context initialization failed
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 15 in XML document from class path resource [mapfish-spring-security.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 15; columnNumber: 40; cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'http-firewall'.
<?xml version="1.0" encoding="UTF-8"?>
<beans:beansxmlns:beans="http://www.springframework.org/schema/beans"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns="http://www.springframework.org/schema/security"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.2.xsd">
<!-- needed to allow double slashes in the URLs -->
<beans:beanid="httpFirewall"class="org.springframework.security.web.firewall.DefaultHttpFirewall">
<beans:propertyname="allowUrlEncodedSlash"value="true"/>
</beans:bean>
<http-firewallref="httpFirewall"/>
<httpuse-expressions="true">
<!-- in order to get a challenge (for capabilities for example) you need to use the print/sec/* urls -->
<csrfdisabled="true"/>
<intercept-urlpattern="/sec/print/**"requires-channel="https"access="isAuthenticated()"/>
<intercept-urlpattern="/**"access="permitAll()"/>
<http-basic/>
<anonymous/>
</http>
<!-- This authentication manager is not authenticating anything. See https://docs.spring.io/spring-security/site/docs/5.1.3.RELEASE/reference/htmlsingle/#ns-config for some help-->
<beans:beanname="org.springframework.security.authenticationManager"class="org.mapfish.print.servlet.NoOpAuthenticationManager"/>
</beans:beans>
Maybe instead of pointing on distant files, those xsd files could be integrated in the solution.
The text was updated successfully, but these errors were encountered:
We were indeed in 3.22 but upgraded to 3.29 for our tests and to be able to open a ticker up to date.
We still have the problem with the latest docker image.
Context
Describe the bug
How to reproduce
Here is my
docker-compose.yml
Actual results
The container can not start.
Workaround
I just found that http://www.springframework.org/schema/security/spring-security.xsd does not exists anymore.
C.F. https://web.archive.org/web/20230218090058/http://www.springframework.org/schema/security/
It existed on 2023-02-18 and was at that time identical to spring-security-5.7.xsd
But on startup, it failed, asking for 5.2.
My solution was to mount a modified version of /mapfish-spring-security.xml to point to an existing xsd version :
And the
mapfish-spring-security.xml
I put is identical to core/src/main/resources/mapfish-spring-security.xml with the version set to 5.2 :Maybe instead of pointing on distant files, those xsd files could be integrated in the solution.
The text was updated successfully, but these errors were encountered: