GAM Multiple Repositories Scenarios

There are cases where only one GAM Repository is not enough to model the reality of our application or company.

Remember that when Enable Integrated Security Property is set to Yes in the application, it connects to an external datastore (named "GAM") where many Repositories can reside. See GAM Repository for details.

The model design of GAM enables to connect to multiple Repositories to solve many scenarios where only one Repository wouldn't be enough. The security module of Multi-tenant applications can be implemented based on this feature, as well as other types of applications which we detail below.

In this document we present some typical applications and scenarios which can be designed using GAM as their Security Module and we explain how to manage multiple Repositories in each case.

Scenario 1. The same application installation is shared by many companies (Multi-Tenant application)

See Multiple Repositories Scenario: The same application installation is shared by many companies

Scenario 2. A company with different branches, users have different GAM Security Policies, GAM Roles and GAM Permissions in each branch

In this scenario of use, the company has different branches, and users have different security policies, roles and permissions depending on the branch where the application runs.
There' s no need to define one GAM database for each branch, because users would need to be redundant in each GAM database. By defining a Repository for each branch, users are the same (and defined only once) in GAM database.

See Multiple Repositories Scenario: A company with different branches

See Also

See Managing GAM Repositories and GAM Applications in GX development time