You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Terence Denzil Monteiro (JIRA)" <ji...@apache.org> on 2018/09/01 20:42:00 UTC

[jira] [Comment Edited] (FINERACT-650) Templates on multi-domain multi-tenant Setups call IP address

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

Terence Denzil Monteiro edited comment on FINERACT-650 at 9/1/18 8:41 PM:
--------------------------------------------------------------------------

Further testing with curl command using POST shows that calling the API directly replicates this without CommunityApp. Here's the command:

{{curl -k -u mifos:password -X POST 'https://testdomain/fineract-provider/api/v1/templates/1?clientId=6' --data-binary '{}' -H 'Content-Type: application/json;charset=UTF-8'}}

Based on this test, it seems to be an issue with Fineract


was (Author: terencemo):
Further testing with curl command generated by browser in community app shows that calling the API directly replicates this without CommunityApp. Here's the command:

{{curl -k -u mifos:password -X POST 'https://testdomain/fineract-provider/api/v1/templates/1?clientId=6' --data-binary '{}' -H 'Content-Type: application/json;charset=UTF-8'}}

> Templates on multi-domain multi-tenant Setups call IP address
> -------------------------------------------------------------
>
>                 Key: FINERACT-650
>                 URL: https://issues.apache.org/jira/browse/FINERACT-650
>             Project: Apache Fineract
>          Issue Type: Bug
>            Reporter: Terence Denzil Monteiro
>            Priority: Major
>
> Setup fineract with multiple tenants, each with a different domain sharing a common IP address using a front-end server like Nginx or Apache, with reverse proxy to Tomcat. Setup also a default server when no domain is called (plain IP address).
> Create sample client / loan templates using client fields like displayName. The mapper shows as tenantIdentifier=default even for non-default tenants. Change it to the correct tenantIdentifier.
> Call the client / loan template and check the server logs.
> An entry will be found in the log for the template of the tenant and another entry will be found in the log for the default server (with plain IP). This shows that in order to generate the template, the application calls the mapper without using the correct domain with which the template was called. I tested this from the Community App and also used curl to call the API directly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)