Skip to content
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

Login fails on production server setup (non-Docker) #2093

Closed
terencemo opened this issue May 21, 2024 · 1 comment
Closed

Login fails on production server setup (non-Docker) #2093

terencemo opened this issue May 21, 2024 · 1 comment
Labels

Comments

@terencemo
Copy link

Description

On multi-tenant production setup, where each tenant runs on a sub-domain of the same parent, e.g abc.mifos.io xyz.mifos.io, we want each tenant to be insulated from the others, so no option to switch backend server. We also want to connect to Fineract on the same sub-domain by default https://xyz.mifos.io connects to https://xyz.mifos.io/fineract-provider/api/v1.

In such a VM setup with Nginx (non-Docker), login tries to use https://demo.fineract.dev/fineract-provider/api/v1/authentication by default and fails, because this URL is down. It should connect to the current production domain by default.

Steps to Reproduce

Setup the web-app on a Server/VM with Nginx as a multi-tenant on subdomain setup (using prefix tenantId.domain.com) with Fineract also on the same domain (non-Docker). Since this is for production, would like each tenant to not need to select the backend but automatically to the same (sub)domain Fineract platform.

Expected Behaviour

Web-app login should connect to Fineract backend server on the same domain and authenticate successfully.

Actual Behaviour

Web-app attempts to connect to https://demo.fineract.dev which has been down since a few years and fails to login

Settings

  • Mifos X version: 23.12.31
  • Browser used: Chrome

Screenshots, if any

terencemo pushed a commit to SanjoseSolutions/web-app that referenced this issue May 21, 2024
@terencemo
Copy link
Author

terencemo commented May 22, 2024

This is the desired behaviour for Production:
Screenshot 2024-05-22 at 2 36 20 PM
Setting the backend server to the same domain by default is accomplished by this PR:
#2095

However, we still have the dropdown visible and I believe it shouldn't be on Production (the above solution was obtained by disabling the backend selector).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant