Page Comparison

...

Scenario: Mod Request-Mediated Flow
Modules are split into smaller applications, each comprising a single backend and frontend module designed to display the UI.

...

Proposed Solutions

...

Tactical Solutions:

1. Deploy the module across all consortium tenants.

   • Pros:

     • No changes needed in the existing logic or code.

   • Cons:

     • The UI will display unnecessary capabilities and capability sets, exposing irrelevant interfaces to end-users.

2. Separate the UI and backend modules.

   • Pros:

     • Minimal changes required—adjust applications to isolate the backend module in a standalone application.

   • Cons:

     • End-users will not see the UI components or associated capabilities, but backend capabilities may still be unintentionally assigned.

3. Proof of Concepts for Workarounds:

   • EUREKA-631:

     • Enable app-tier logic for all tenants, ensuring system users are created. Then, disable the application for data tenants without purging (purge=false). This ensures system users exist while disabling the application for data tenants.

     • Experiment with enabling only the backend module for all tenants, excluding the UI module. This has been partially explored by the Vega team.

...

Strategic Solutions:

1. Introduce Reconciliation Logic for System Users:

   • Ensure all system users exist across all consortium tenants by implementing reconciliation functionality triggered in scenarios such as:

     • When a new tenant is added to the consortium.

     • When a tenant is removed from the consortium.

     • When a tenant is updated within the consortium.

This ensures system users are consistently created for all tenants in the consortium.

...