Repository navigation
LDAP-profile WAR fails to start after Spring 7 upgrade due to missing entityManager bean #12728
Description
Description
The application starts Tomcat and begins Spring/Hibernate initialization successfully, but fails while creating the Spring Security filter chain. The LDAP security configuration references filters that depend on an entityManager bean, but the LDAP geostore-spring-security.xml does not define that bean.
mapstore.war built with ldap profiles, fails to load with the following Error.
error.log
How to reproduce
Build with profiles: ldap,printing, > Run with valid ldap.properties + ldap setup.
Expected Result
Mapstore should run with ldap enabled profiles.
Current Result
Mapstore fails to load, Error 404. Check error.log above.
- Not browser related
Browser info
(use this site: https://www.whatsmybrowser.org/ for non expert users)| Browser Affected | Version |
|---|---|
| Internet Explorer | |
| Edge | |
| Chrome | |
| Firefox | |
| Safari |
Other useful information
Updating /usr/local/tomcat/webapps/mapstore/WEB-INF/classes/geostore-spring-security.xml with the following seems to work as a temporary measure.
....
</security:http>
<bean id="entityManager"
class="org.springframework.orm.jpa.support.SharedEntityManagerBean">
<property name="entityManagerFactory" ref="geostoreEntityManagerFactory"/>
<property name="persistenceUnitName" value="geostore"/>
</bean>
<!-- Entry point -->
<bean id="restAuthenticationEntryPoint" class="it.geosolutions.geostore.services.rest.security.RestAuthenticationEntryPoint" >
....
Security vulnerabilities
Do not report security vulnerabilities in public issues.
If you believe you have found a vulnerability in MapStore, please use GitHub private vulnerability reporting or contact the security address listed in SECURITY.md.
Activity
offtherailz commentedon Jul 24, 2026
Reproduced on master. The cause is the Spring 7 upgrade (#12428): it added depends-on="entityManager" to the token filters in both the db and ldap security configs, but added the entityManager bean definition only to the db configs. So the ldap configs reference a bean that is never defined.
Two notes for the fix:
product/config/ldap/geostore-spring-security-ldap.xmlandweb/src/config/ldap/geostore-spring-security-ldap.xml.Opened #12729 with the fix. Tested against the acme-ldap server from the docs: login as bill/hello works with the ADMIN role.
Fix #12728: add missing entityManager bean to LDAP security config (#…
Fix geosolutions-it#12728: add missing entityManager bean to LDAP sec…
Fix geosolutions-it#12728: add missing entityManager bean to LDAP sec…