-
Notifications
You must be signed in to change notification settings - Fork 46
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
Is it possible to implement fineract-pentaho with the latest fineract-provider (1.4.0) branch ? #18
Comments
the SQL injection is something that has been solved with the latest build. is details are explained apache/fineract#1671 in my view if you use an build other than the latest or a release before apache/fineract#1671 was merged, you are likely to be faced with sql-injection issues |
I would suggest that you do a cherry-pick of the changes made in apache/fineract#1671 and rebuild |
Hello! Thank You so much for the interest in this project. Please read #25 for an announcement re. future maintenance of this repo. |
@sathishnr98 you could cherry-pick as suggested by @francisguchie or you could get the latest Fineract build 1.5 which has the fix for the issue. |
@sathishnr98 , |
Hello @vorburger and @francisguchie ,
I tried to implement fineract-pentaho with the latest fineract-provider (1.4.0) branch, as I know to implement the things in develop branch but for my convinence I need to implement this things in 1.4.0.
Is it possible to do so, then I'm just trying to do this thing and I got some errors which I have mentioned the errors what are all the things which I have faced right now,
While hitting this endpoint,
Request URL: https://localhost:8443/fineract-provider/api/v1/runreports/Client%20Listing(Pentaho)?output-type=PDF&tenantIdentifier=default&locale=en&dateFormat=dd%20MMMM%20yyyy&R_selectOffice=1
I got this error,
This is my tomcat log for your convenience,
Please let me know whether there are any possible solutions to resolve the issue, if possible then could you please help me to resolve it.
The text was updated successfully, but these errors were encountered: