roger.mirrer Posted June 5, 2019 Share Posted June 5, 2019 When we upgrade JasperReportsServer from version 7.1 to 7.2 the application started with the following errors:2019-06-05 07:28:16,583 INFO [stdout] (ServerService Thread Pool -- 90) 2019-06-05 07:28:16,578 ERROR ContextLoader,ServerService Thread Pool -- 90:350 - Context initialization failed2019-06-05 07:28:16,583 INFO [stdout] (ServerService Thread Pool -- 90) org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'proxyBasicProcessingFilter' defined in ServletContext resource [/WEB-INF/applicationContext-externalAuth-LDAP.xml]: Error setting property values; nested exception is org.springframework.beans.NotWritablePropertyException: Invalid property 'authenticationManager' of bean class [com.jaspersoft.jasperserver.api.security.externalAuth.ExternalAuthBasicProcessingFilter]: Bean property 'authenticationManager' is not writable or has an invalid setter method. Does the parameter type of the setter match the return type of the getter?The WEB-INF/applicationContext-externalAuth-LDAP.xml file seems to be different in 7.1 and 7.2. Link to comment Share on other sites More sharing options...
elizam Posted June 10, 2019 Share Posted June 10, 2019 in 7.2, they upgraded Spring Security to a new version. It is suggested that you reimplement your external auth using the new files as a base. An overview is here:https://community.jaspersoft.com/documentation/tibco-jasperreports-server-upgrade-guide/v720/changes-72-may-affect-your-upgrade Link to comment Share on other sites More sharing options...
pokornyjan Posted June 24, 2019 Share Posted June 24, 2019 I have same problem. After upgrade I used "applicationContext-externalAuth-LDAP.xml" (v.7.2, same configuration).Please help. Thanks in advance, Jan Link to comment Share on other sites More sharing options...
jreporter Posted June 27, 2019 Share Posted June 27, 2019 I have the same problem here after upgrade from 6.3 to 7.2.I used the new sample file from 7.2 sample-applicationContext-externalAuth-LDAP.xml and reimplemented our settings.But after server restart I got the same error like @roger.mirrorSee also this bug report : [#11866] - ldap integration breaks jasperserverhttps://community.jaspersoft.com/jasperreports-server/issues/11866Any help is appreciated.ThanksMarwin Link to comment Share on other sites More sharing options...
pokornyjan Posted July 22, 2019 Share Posted July 22, 2019 I tried new installation, same problem :-( Link to comment Share on other sites More sharing options...
brodie Posted August 2, 2019 Share Posted August 2, 2019 I just started working on LDAP authenticaiton for our Jasper setup. We're running 7.2. It appears that the suppled example file "sample-applicationContext-externalAuth-LDAP.xml" that ships with Jasper 7.2 does not work, and causes the error above (Error setting property values; nested exception is org.springframework.beans.NotWritablePropertyException: Invalid property 'authenticationManager' of bean class ).this is kind of a show-stopper for us. Link to comment Share on other sites More sharing options...
antey86 Posted September 17, 2019 Share Posted September 17, 2019 Hi guys,It looks like Spring Security was upgraded in JR v7.2 up to 4.2. Which led to change in ExternalAuthBasicProcessingFilter.So you need to use constructor arg for authenticationManager bean instead of setter: <bean id="proxyBasicProcessingFilter" class="com.jaspersoft.jasperserver.api.security.externalAuth.ExternalAuthBasicProcessingFilter" parent="basicProcessingFilter"> <constructor-arg index="0" ref="ldapAuthenticationManager"/> <property name="externalDataSynchronizer" ref="externalDataSynchronizer"/> </bean> Link to comment Share on other sites More sharing options...
raymondg Posted January 11, 2022 Share Posted January 11, 2022 I know this is a couple years old, but I just installed jasperserver 8.0 and had this same error. antey86's suggestion worked for me. Link to comment Share on other sites More sharing options...
kkren Posted January 11 Share Posted January 11 This is still an issue as of 8.2.0 with the same fix as above. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now