[ 
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598350#comment-17598350
 ] 

Aleksandar Vidakovic commented on FINERACT-1653:
------------------------------------------------

[~francisguchie] the best place for those environment variables in WAR 
deployment is the "setenv.sh" file in the "bin" folder of your Tomcat 
installation. If it doesn't exist then just create one. This file will be 
picked up by Tomcat automatically and is meant to contain such additional 
definitions/environment variables/override of Tomcat startup parameters etc. 
We've added a sample "setenv.sh" file fairly recently, because questions like 
yours came up once in a while (I think that we even mention it in the Asciidoc 
documentation). Please have a look here: 
[https://github.com/apache/fineract/blob/develop/fineract-war/setenv.sh]

Hope this helps.

> Security Threat Cannot boot Apache Fineract if database is not on local host 
> and password is not the default
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-1653
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1653
>             Project: Apache Fineract
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>            Reporter: Francis Guchie
>            Assignee: Francis Guchie
>            Priority: Major
>             Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where 
> the database server is separate from the ui server with a different root 
> password from usual. 
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of 
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of 
> Apache-Fineract. 
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting 
> constructor argument; nested exception is 
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL 
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
>  Unsatisfied dependency expressed through constructor parameter 0; 
> nested exception is 
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
> creating bean with name 'jdbcTenantDetailsService' 
> defined in URL 
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default 
> root password and if they have the database and ui on different servers. 
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the 
> following files after a first boot up when the war file is deployed (
> *......webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.....webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to