Federation server is mifos installation local

Owned by Myrle Krantz (Deactivated)
Dec 14, 2015
1 min read
StatusDECIDED
StakeholdersMarkus Geiss (Deactivated) Myrle Krantz (Deactivated) Ed Cable Craig Chelius 
OutcomeCustomer deployment. We may later decide to provide a central deployment as well, the use of which would be optional to the customers. But our first implementation will be a customer deployment.
Due date
OwnerMyrle Krantz (Deactivated) 

Background

We have two choices:

  1. A global deployment hosted by us
    1. We would setup one uber federation server hosted at mifos.org
    2. Every customer would need to add an entry with the following details: company and tenant (e.g. conflux, novopay)
    3. The mapped address would look like this: conflux-novopay*mifos.org
  2. A per deployment hosting by our customers
    1. Every customer would setup its own federation server hosted at their domain (e.g. confluxtechnologies.com)
    2. Every customer would need to add an entry with the tenant name
    3. The mapped address would look like this: novopay*confluxtechnologies.com


Both solution have its pros and cons:

  1. Would make the deployment very easy, but forces our customers to store some (maybe nondisclosure) information at Mifos.
  2. Would need a deployment at the customer site (we'd need to provide a How to guide), needing to connect this component to the internet.

Action items

  •