User Providers

Each Repository could potentially have its own user database, for example, one application may connect to Active Directory, the other may connect to AVEVA Work Tasks Databases, and others to Lightweight Directory Access Protocol (LDAP) or Active Directory Application Mode (ADAM).

When AVEVA Work Tasks uses each of these Repositories, it needs to ensure that users of these Repositories can work with AVEVA Work Tasks without any complicated configurations. AVEVA Work Tasks also ensures that connection to these repositories are secure. The secure connection indicates that only authorized functionality is available to each and every resource.

Different repositories may be using the same authentication source, but may have different metadata and grouping information with them. For Example, the authentication source could be active directory, but there could be five other repositories which are using the same user and maintain Repository specific user metadata.

The user integration needs to be outside the Repository boundary since users can span across multiple Repositories. In AVEVA Work Tasks, we use a concept known as User Entity and Role Entity for managing users across different platforms.

User Entity manages all the information for the users across different data sources. Data Source may be Active Directory, SQL providers, and so on. The Role Entity manages users in roles.

Data bridge framework is the common framework that bridges the entity item and the corresponding data source providers. Each entity item will internally communicate with the Data bridge framework to know from which Data Source provider the entity details should be retrieved.