Enable an Existing Repository with Cross-domain Role Provider
- Last UpdatedJun 06, 2024
- 1 minute read
Introduction to Cross Domain
An Active Directory role with users from different domains (cross domains) can be mapped to a AVEVA Work Tasks Role using AVEVA Work Tasks Role Provider.
For example, Users 'John' and 'Jim' of domain 'TelematicsUS' and users 'Mike' and 'Bob' from domain 'TelematicsAU' are added to role "Team HR" of domain 'TelematicsMain'. Now the "Team HR" role of domain 'TelematicsMain' contains four users 'John', 'Jim', 'Mike' and 'Bob'.
Consider the following scenario

-
Child01: Domain Child01 has a user 'Jim' and a role 'Team HR'. User 'Jim' belongs to the role 'Team HR'.
-
Child02: Domain Child02 has a user 'Mike' and a role 'Team R & D'. The 'Team R &D' role has the following users:
-
'Mike' of domain Child02
-
'John' of domain Parent
-
'Jim' of domain Child01
-
To enable an existing repository(without cross-domain role provider) to a Cross-Domain Role Provider.
Prerequisite:
-
All available active directory must be added as a provider for the repository.
-
The domain controllers must be in the same Forest with parent-child relationship.
-
Separate Forests are not supported.
-
The IsCrossDomain property must be set as True for all the active directory role provider in SKEntityDataSourceProvider table in the DefinitionXml column.
After configuring the prerequisites, see Synchronize Roles.